Enhancements for Radio Access Capability Signaling (RACS)

ABSTRACT

Embodiments are presented herein of apparatuses, systems, and methods for a user equipment device (UE), manufacturer server, and/or cellular network to perform radio capability signaling. A new type of UE radio capability identifier is provided which may allow a network to distinguish between similar UEs that have or have not implemented a capability update. In order to perform a forced capability update, a manufacturer may issue information about the update to a cellular network (and receive acknowledgement of the information) prior to pushing the update to UEs. In response to an unforced capability update, a cellular network may maintain multiple UE radio capability identifiers for similar UEs which have or have not implemented the update. A UE radio capability identifier may be adjusted dynamically in response to temporary changes in the UE&#39;s capability.

PRIORITY CLAIM

This application claims priority to U.S. provisional patent applicationSer. No. 62/909,938, entitled “Enhancements for Radio Access CapabilitySignaling (RACS),” filed Oct. 3, 2019, which is hereby incorporated byreference in its entirety as though fully and completely set forthherein.

TECHNICAL FIELD

The present application relates to wireless devices, and moreparticularly to apparatuses, systems, and methods for managing radioaccess capability signaling (RACS).

DESCRIPTION OF THE RELATED ART

Wireless communication systems are rapidly growing in usage. Wirelessdevices, particularly wireless user equipment devices (UEs), have becomewidespread. Additionally, there are a variety of applications (or apps)hosted on UEs that perform or depend on wireless communication, such asapplications that provide messaging, email, browsing, video streaming,short video, voice streaming, real-time gaming, or various other onlineservices.

In some instances, radio access capability signaling (RACS) may be usedto describe changes in a UE's capabilities for various reasons. However,some changes in capabilities may not be accurately or efficientlydescribed using existing techniques. Accordingly, improvements in thefield may be desired.

SUMMARY

Techniques, apparatuses, systems, and methods are disclosed for a userequipment device (UE), manufacturer server, and cellular network toexchange information about UE capabilities, e.g., using radio accesscapability signaling (RACS).

In some embodiments, a manufacturer server may receive UE radioconfiguration information. The server may create a corresponding UEradio capability Identifier (ID) and transmit the ID to one or morenetworks. The server may push (e.g., transmit) the radio configurationto one or more UEs.

In some embodiments, a manufacturer server may receive UE radioconfiguration information. The server may request a dictionary entry(e.g., a dictionary entry in a data base of UE radio configurationinformation and capabilities, including UE radio capability IDs) andreceive confirmation of the dictionary entry. The server may transmit aforced update to one or more UEs and implement a corresponding UE radiocapability ID.

In some embodiments, a network may receive a registration from a UE anddetermine a UE radio capability ID. The network may create a new UEradio capability ID associated with a capability update and transmit theupdate to one or more UEs. The network may receive updated registrationbased on the capability update from a subset of the one or more UEs. Thenetwork may maintain distinct UE radio capability IDs for UEs which haveand have not implemented the update.

In some embodiments, a UE may register with a network and laterdetermine to operate at a reduced capability. The UE may update theregistration and may later revert to its full capability.

This Summary is intended to provide a brief overview of some of thesubject matter described in this document. Accordingly, it will beappreciated that the above-described features are merely examples andshould not be construed to narrow the scope or spirit of the subjectmatter described herein in any way. Other features, aspects, andadvantages of the subject matter described herein will become apparentfrom the following Detailed Description, Figures, and Claims.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the disclosed embodiments can be obtained whenthe following detailed description is considered in conjunction with thefollowing drawings, in which:

FIG. 1 illustrates an example wireless communication system, accordingto some embodiments;

FIG. 2 illustrates a base station (BS) in communication with a userequipment (UE) device, according to some embodiments;

FIG. 3 illustrates an example block diagram of a UE, according to someembodiments;

FIG. 4 illustrates an example block diagram of a BS, according to someembodiments;

FIG. 5 illustrates an example block diagram of cellular communicationcircuitry, according to some embodiments;

FIGS. 6 and 7 illustrate examples of a 5G NR base station (gNB),according to some embodiments;

FIGS. 8 and 9 illustrate example aspects of network architecture,according to some embodiments;

FIG. 10 is a block diagram illustrating aspects of international mobileequipment identity and software version number (IMEISV), according tosome embodiments;

FIG. 11 is flow chart diagram illustrating an example method of using anew UE radio capability ID format, according to some embodiments;

FIG. 12 is flow chart diagram illustrating an example method for forcedcapability update, according to some embodiments;

FIGS. 13-16 illustrate example call flows for forced capability updates,according to some embodiments;

FIG. 17 is flow chart diagram illustrating an example method forunforced capability update, according to some embodiments;

FIG. 18 illustrates an example call flow for an unforced capabilityupdate, according to some embodiments;

FIG. 19 is flow chart diagram illustrating an example method fordynamically changing UE radio capability ID, according to someembodiments; and

FIGS. 20-23 illustrate aspects of dynamically changing UE radiocapability ID, according to some embodiments.

While the invention is susceptible to various modifications andalternative forms, specific embodiments thereof are shown by way ofexample in the drawings and are herein described in detail. It should beunderstood, however, that the drawings and detailed description theretoare not intended to limit the invention to the particular formdisclosed, but on the contrary, the intention is to cover allmodifications, equivalents and alternatives falling within the spiritand scope of the present invention as defined by the appended claims.

DETAILED DESCRIPTION OF THE EMBODIMENTS Acronyms

The following acronyms may be used in the present Patent Application:

UE: User Equipment

BS: Base Station

ENB: eNodeB (Base Station)

LTE: Long Term Evolution

VoLTE: voice over LTE

UMTS: Universal Mobile Telecommunications System

RAT: Radio Access Technology

RAN: Radio Access Network

E-UTRAN: Evolved UMTS Terrestrial RAN

CN: Core Network

EPC: Evolved Packet Core

MME: Mobile Management Entity

HSS: Home Subscriber Server

SGW: Serving Gateway

PS: Packet-Switched

CS: Circuit-Switched

EPS: Evolved Packet-Switched System

RRC: Radio Resource Control

IE: Information Element

UL: uplink

DL: downlink

RS: reference signal

RACS: Radio Access Capability Signaling

PLMN: Public Land Mobile Network

UCMF: UE radio Capability Management Function

Application Function (AF)

Access and Mobility Management Function (AMF)

Type allocation code (TAC)

Serial number (SNR)

software version number (SVN)

Network Exposure Function (NEF)

Network Data Analytics Function (NWDAF)

discontinuous reception (DRX)

international mobile equipment identity and software version number(IMEISV)

Terms

The following is a glossary of terms used in this disclosure:

Memory Medium—Any of various types of non-transitory memory devices orstorage devices. The term “memory medium” is intended to include aninstallation medium, e.g., a CD-ROM, floppy disks, or tape device; acomputer system memory or random access memory such as DRAM, DDR RAM,SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash,magnetic media, e.g., a hard drive, or optical storage; registers, orother similar types of memory elements, etc. The memory medium mayinclude other types of non-transitory memory as well or combinationsthereof. In addition, the memory medium may be located in a firstcomputer system in which the programs are executed, or may be located ina second different computer system which connects to the first computersystem over a network, such as the Internet. In the latter instance, thesecond computer system may provide program instructions to the firstcomputer for execution. The term “memory medium” may include two or morememory mediums which may reside in different locations, e.g., indifferent computer systems that are connected over a network. The memorymedium may store program instructions (e.g., embodied as computerprograms) that may be executed by one or more processors.

Carrier Medium—a memory medium as described above, as well as a physicaltransmission medium, such as a bus, network, and/or other physicaltransmission medium that conveys signals such as electrical,electromagnetic, or digital signals.

Programmable Hardware Element—includes various hardware devicescomprising multiple programmable function blocks connected via aprogrammable interconnect. Examples include FPGAs (Field ProgrammableGate Arrays), PLDs (Programmable Logic Devices), FPOAs (FieldProgrammable Object Arrays), and CPLDs (Complex PLDs). The programmablefunction blocks may range from fine grained (combinatorial logic or lookup tables) to coarse grained (arithmetic logic units or processorcores). A programmable hardware element may also be referred to as“reconfigurable logic”.

Computer System—any of various types of computing or processing systems,including a personal computer system (PC), mainframe computer system,workstation, network appliance, Internet appliance, personal digitalassistant (PDA), television system, grid computing system, or otherdevice or combinations of devices. In general, the term “computersystem” can be broadly defined to encompass any device (or combinationof devices) having at least one processor that executes instructionsfrom a memory medium.

User Equipment (UE) (or “UE Device”)—any of various types of computersystems devices which are mobile or portable and which performs wirelesscommunications. Examples of UE devices include mobile telephones orsmart phones (e.g., iPhone™ Android™-based phones), portable gamingdevices (e.g., Nintendo DS™, PlayStation Portable™, Gameboy Advance™,iPhone™), laptops, wearable devices (e.g. smart watch, smart glasses),PDAs, portable Internet devices, music players, data storage devices, orother handheld devices, etc. In general, the term “UE” or “UE device”can be broadly defined to encompass any electronic, computing, and/ortelecommunications device (or combination of devices) which is easilytransported by a user and capable of wireless communication.

Wireless Device—any of various types of computer system devices whichperforms wireless communications. A wireless device can be portable (ormobile) or may be stationary or fixed at a certain location. A UE is anexample of a wireless device.

Communication Device—any of various types of computer systems or devicesthat perform communications, where the communications can be wired orwireless. A communication device can be portable (or mobile) or may bestationary or fixed at a certain location. A wireless device is anexample of a communication device. A UE is another example of acommunication device.

Base Station—The term “Base Station” has the full breadth of itsordinary meaning, and at least includes a wireless communication stationinstalled at a fixed location and used to communicate as part of awireless telephone system or radio system.

Processing Element—refers to various elements or combinations ofelements that are capable of performing a function in a device, such asa user equipment or a cellular network device. Processing elements mayinclude, for example: processors and associated memory, portions orcircuits of individual processor cores, entire processor cores,processor arrays, circuits such as an ASIC (Application SpecificIntegrated Circuit), programmable hardware elements such as a fieldprogrammable gate array (FPGA), as well any of various combinations ofthe above.

Channel—a medium used to convey information from a sender (transmitter)to a receiver. It should be noted that since characteristics of the term“channel” may differ according to different wireless protocols, the term“channel” as used herein may be considered as being used in a mannerthat is consistent with the standard of the type of device withreference to which the term is used. In some standards, channel widthsmay be variable (e.g., depending on device capability, band conditions,etc.). For example, LTE may support scalable channel bandwidths from 1.4MHz to 20 MHz. In contrast, WLAN channels may be 22 MHz wide whileBluetooth channels may be 1 Mhz wide. Other protocols and standards mayinclude different definitions of channels. Furthermore, some standardsmay define and use multiple types of channels, e.g., different channelsfor uplink or downlink and/or different channels for different uses suchas data, control information, etc.

Band—The term “band” has the full breadth of its ordinary meaning, andat least includes a section of spectrum (e.g., radio frequency spectrum)in which channels are used or set aside for the same purpose.

Automatically—refers to an action or operation performed by a computersystem (e.g., software executed by the computer system) or device (e.g.,circuitry, programmable hardware elements, ASICs, etc.), without userinput directly specifying or performing the action or operation. Thus,the term “automatically” is in contrast to an operation being manuallyperformed or specified by the user, where the user provides input todirectly perform the operation. An automatic procedure may be initiatedby input provided by the user, but the subsequent actions that areperformed “automatically” are not specified by the user, i.e., are notperformed “manually”, where the user specifies each action to perform.For example, a user filling out an electronic form by selecting eachfield and providing input specifying information (e.g., by typinginformation, selecting check boxes, radio selections, etc.) is fillingout the form manually, even though the computer system must update theform in response to the user actions. The form may be automaticallyfilled out by the computer system where the computer system (e.g.,software executing on the computer system) analyzes the fields of theform and fills in the form without any user input specifying the answersto the fields. As indicated above, the user may invoke the automaticfilling of the form, but is not involved in the actual filling of theform (e.g., the user is not manually specifying answers to fields butrather they are being automatically completed). The presentspecification provides various examples of operations beingautomatically performed in response to actions the user has taken.

Approximately—refers to a value that is almost correct or exact. Forexample, approximately may refer to a value that is within 1 to 10percent of the exact (or desired) value. It should be noted, however,that the actual threshold value (or tolerance) may be applicationdependent. For example, in some embodiments, “approximately” may meanwithin 0.1% of some specified or desired value, while in various otherembodiments, the threshold may be, for example, 2%, 3%, 5%, and soforth, as desired or as required by the particular application.

Concurrent—refers to parallel execution or performance, where tasks,processes, or programs are performed in an at least partiallyoverlapping manner. For example, concurrency may be implemented using“strong” or strict parallelism, where tasks are performed (at leastpartially) in parallel on respective computational elements, or using“weak parallelism”, where the tasks are performed in an interleavedmanner, e.g., by time multiplexing of execution threads.

Configured to—Various components may be described as “configured to”perform a task or tasks. In such contexts, “configured to” is a broadrecitation generally meaning “having structure that” performs the taskor tasks during operation. As such, the component can be configured toperform the task even when the component is not currently performingthat task (e.g., a set of electrical conductors may be configured toelectrically connect a module to another module, even when the twomodules are not connected). In some contexts, “configured to” may be abroad recitation of structure generally meaning “having circuitry that”performs the task or tasks during operation. As such, the component canbe configured to perform the task even when the component is notcurrently on. In general, the circuitry that forms the structurecorresponding to “configured to” may include hardware circuits.

Various components may be described as performing a task or tasks, forconvenience in the description. Such descriptions should be interpretedas including the phrase “configured to.” Reciting a component that isconfigured to perform one or more tasks is expressly intended not toinvoke 35 U.S.C. § 112(f) interpretation for that component.

FIGS. 1 and 2—Communication System

FIG. 1 illustrates a simplified example wireless communication system,according to some embodiments. It is noted that the system of FIG. 1 ismerely one example of a possible system, and that features of thisdisclosure may be implemented in any of various systems, as desired.

As shown, the example wireless communication system includes a basestation 102 which communicates over a transmission medium with one ormore user devices 106A, 106B, etc., through 106N. Each of the userdevices may be referred to herein as a “user equipment” (UE). Thus, theuser devices 106 are referred to as UEs or UE devices.

The base station (BS) 102 may be a base transceiver station (BTS) orcell site (a “cellular base station”), and may include hardware thatenables wireless communication with the UEs 106A through 106N.

The communication area (or coverage area) of the base station may bereferred to as a “cell.” The base station 102 and the UEs 106 may beconfigured to communicate over the transmission medium using any ofvarious radio access technologies (RATs), also referred to as wirelesscommunication technologies, or telecommunication standards, such as GSM,UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces),LTE, LTE-Advanced (LTE-A), 5G new radio (5G NR), HSPA, 3GPP2 CDMA2000(e.g., 1×RTT, 1×EV-DO, HRPD, eHRPD), etc. Note that if the base station102 is implemented in the context of LTE, it may alternately be referredto as an ‘eNodeB’ or ‘eNB’. Note that if the base station 102 isimplemented in the context of 5G NR, it may alternately be referred toas ‘gNodeB’ or ‘gNB’.

As shown, the base station 102 may also be equipped to communicate witha network 100 (e.g., a core network of a cellular service provider, atelecommunication network such as a public switched telephone network(PSTN), and/or the Internet, among various possibilities). Thus, thebase station 102 may facilitate communication between the user devicesand/or between the user devices and the network 100. In particular, thecellular base station 102 may provide UEs 106 with varioustelecommunication capabilities, such as voice, SMS and/or data services.

Base station 102 and other similar base stations operating according tothe same or a different cellular communication standard may thus beprovided as a network of cells, which may provide continuous or nearlycontinuous overlapping service to UEs 106A-N and similar devices over ageographic area via one or more cellular communication standards.

Thus, while base station 102 may act as a “serving cell” for UEs 106A-Nas illustrated in FIG. 1, each UE 106 may also be capable of receivingsignals from (and possibly within communication range of) one or moreother cells (which might be provided by other base stations 102B-N),which may be referred to as “neighboring cells”. Such cells may also becapable of facilitating communication between user devices and/orbetween user devices and the network 100. Such cells may include “macro”cells, “micro” cells, “pico” cells, and/or cells which provide any ofvarious other granularities of service area size. Other configurationsare also possible.

In some embodiments, base station 102 may be a next generation basestation, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In someembodiments, a gNB may be connected to a legacy evolved packet core(EPC) network and/or to a NR core (NRC) network. In addition, a gNB cellmay include one or more transition and reception points (TRPs). Inaddition, a UE capable of operating according to 5G NR may be connectedto one or more TRPs within one or more gNBs.

Note that a UE 106 may be capable of communicating using multiplewireless communication standards. For example, the UE 106 may beconfigured to communicate using a wireless networking (e.g., Wi-Fi)and/or peer-to-peer wireless communication protocol (e.g., Bluetooth,Wi-Fi peer-to-peer, etc.) in addition to at least one cellularcommunication protocol (e.g., GSM, UMTS (associated with, for example,WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2CDMA2000 (e.g., 1×RTT, 1×EV-DO, HRPD, eHRPD), etc.). The UE 106 may alsoor alternatively be configured to communicate using one or more globalnavigational satellite systems (GNSS, e.g., GPS or GLONASS), one or moremobile television broadcasting standards (e.g., ATSC-M/H), and/or anyother wireless communication protocol, if desired. Other combinations ofwireless communication standards (including more than two wirelesscommunication standards) are also possible.

The network 100 and/or UE 106 may also communicate with a server 109associated with a UE manufacturer. The manufacturer server 109 mayprovide software and/or capability updates to the UE 106. Similarly, themanufacturer server 109 may provide information about such updates tothe network 100. For example, the manufacturer server 109 may provideidentifying information associated with the UE 106 and/or an update tothe UE and/or network.

FIG. 2 illustrates user equipment 106 (e.g., one of the devices 106Athrough 106N) in communication with a base station 102, according tosome embodiments. The UE 106 may be a device with cellular communicationcapability such as a mobile phone, a hand-held device, a computer or atablet, or virtually any type of wireless device.

The UE 106 may include a processor that is configured to execute programinstructions stored in memory. The UE 106 may perform any of the methodembodiments described herein by executing such stored instructions.Alternatively, or in addition, the UE 106 may include a programmablehardware element such as an FPGA (field-programmable gate array) that isconfigured to perform any of the method embodiments described herein, orany portion of any of the method embodiments described herein.

The UE 106 may include one or more antennas for communicating using oneor more wireless communication protocols or technologies. In someembodiments, the UE 106 may be configured to communicate using, forexample, CDMA2000 (1×RTT/1×EV-DO/HRPD/eHRPD) or LTE using a singleshared radio and/or GSM or LTE using the single shared radio. The sharedradio may couple to a single antenna, or may couple to multiple antennas(e.g., for multiple-input, multiple-output or “MIMO”) for performingwireless communications. In general, a radio may include any combinationof a baseband processor, analog RF signal processing circuitry (e.g.,including filters, mixers, oscillators, amplifiers, etc.), or digitalprocessing circuitry (e.g., for digital modulation as well as otherdigital processing). Similarly, the radio may implement one or morereceive and transmit chains using the aforementioned hardware. Forexample, the UE 106 may share one or more parts of a receive and/ortransmit chain between multiple wireless communication technologies,such as those discussed above.

In some embodiments, the UE 106 may include any number of antennas andmay be configured to use the antennas to transmit and/or receivedirectional wireless signals (e.g., beams). Similarly, the BS 102 mayalso include any number of antennas and may be configured to use theantennas to transmit and/or receive directional wireless signals (e.g.,beams). To receive and/or transmit such directional signals, theantennas of the UE 106 and/or BS 102 may be configured to applydifferent “weight” to different antennas. The process of applying thesedifferent weights may be referred to as “precoding”.

In some embodiments, the UE 106 may include separate transmit and/orreceive chains (e.g., including separate antennas and other radiocomponents) for each wireless communication protocol with which it isconfigured to communicate. As a further possibility, the UE 106 mayinclude one or more radios which are shared between multiple wirelesscommunication protocols, and one or more radios which are usedexclusively by a single wireless communication protocol. For example,the UE 106 might include a shared radio for communicating using eitherof LTE or 5G NR (or LTE or 1×RTT or LTE or GSM), and separate radios forcommunicating using each of Wi-Fi and Bluetooth. Other configurationsare also possible.

FIG. 3—Block Diagram of a UE

FIG. 3 illustrates an example simplified block diagram of acommunication device 106, according to some embodiments. It is notedthat the block diagram of the communication device of FIG. 3 is only oneexample of a possible communication device. According to embodiments,communication device 106 may be a user equipment (UE) device, a mobiledevice or mobile station, a wireless device or wireless station, adesktop computer or computing device, a mobile computing device (e.g., alaptop, notebook, or portable computing device), a tablet and/or acombination of devices, among other devices. As shown, the communicationdevice 106 may include a set of components 300 configured to performcore functions. For example, this set of components may be implementedas a system on chip (SOC), which may include portions for variouspurposes. Alternatively, this set of components 300 may be implementedas separate components or groups of components for the various purposes.The set of components 300 may be coupled (e.g., communicatively;directly or indirectly) to various other circuits of the communicationdevice 106.

For example, the communication device 106 may include various types ofmemory (e.g., including NAND flash 310), an input/output interface suchas connector I/F 320 (e.g., for connecting to a computer system; dock;charging station; input devices, such as a microphone, camera, keyboard;output devices, such as speakers; etc.), the display 360, which may beintegrated with or external to the communication device 106, andcellular communication circuitry 330 such as for 5G NR, LTE, GSM, etc.,and short to medium range wireless communication circuitry 329 (e.g.,Bluetooth™ and WLAN circuitry). In some embodiments, communicationdevice 106 may include wired communication circuitry (not shown), suchas a network interface card, e.g., for Ethernet.

The cellular communication circuitry 330 may couple (e.g.,communicatively; directly or indirectly) to one or more antennas, suchas antennas 335 and 336 as shown. The short to medium range wirelesscommunication circuitry 329 may also couple (e.g., communicatively;directly or indirectly) to one or more antennas, such as antennas 337and 338 as shown. Alternatively, the short to medium range wirelesscommunication circuitry 329 may couple (e.g., communicatively; directlyor indirectly) to the antennas 335 and 336 in addition to, or insteadof, coupling (e.g., communicatively; directly or indirectly) to theantennas 337 and 338. The short to medium range wireless communicationcircuitry 329 and/or cellular communication circuitry 330 may includemultiple receive chains and/or multiple transmit chains for receivingand/or transmitting multiple spatial streams, such as in amultiple-input multiple output (MIMO) configuration.

In some embodiments, as further described below, cellular communicationcircuitry 330 may include dedicated receive chains (including and/orcoupled to, e.g., communicatively, directly or indirectly, dedicatedprocessors and/or radios) for multiple RATs (e.g., a first receive chainfor LTE and a second receive chain for 5G NR). In addition, in someembodiments, cellular communication circuitry 330 may include a singletransmit chain that may be switched between radios dedicated to specificRATs. For example, a first radio may be dedicated to a first RAT, e.g.,LTE, and may be in communication with a dedicated receive chain and atransmit chain shared with an additional radio, e.g., a second radiothat may be dedicated to a second RAT, e.g., 5G NR, and may be incommunication with a dedicated receive chain and the shared transmitchain.

The communication device 106 may also include and/or be configured foruse with one or more user interface elements. The user interfaceelements may include any of various elements, such as display 360 (whichmay be a touchscreen display), a keyboard (which may be a discretekeyboard or may be implemented as part of a touchscreen display), amouse, a microphone and/or speakers, one or more cameras, one or morebuttons, and/or any of various other elements capable of providinginformation to a user and/or receiving or interpreting user input.

The communication device 106 may further include one or more smart cards345 that include SIM (Subscriber Identity Module) functionality, such asone or more UICC(s) (Universal Integrated Circuit Card(s)) cards 345.

As shown, the SOC 300 may include processor(s) 302, which may executeprogram instructions for the communication device 106 and displaycircuitry 304, which may perform graphics processing and provide displaysignals to the display 360. The processor(s) 302 may also be coupled tomemory management unit (MMU) 340, which may be configured to receiveaddresses from the processor(s) 302 and translate those addresses tolocations in memory (e.g., memory 306, read only memory (ROM) 350, NANDflash memory 310) and/or to other circuits or devices, such as thedisplay circuitry 304, short range wireless communication circuitry 229,cellular communication circuitry 330, connector I/F 320, and/or display360. The MMU 340 may be configured to perform memory protection and pagetable translation or set up. In some embodiments, the MMU 340 may beincluded as a portion of the processor(s) 302.

As noted above, the communication device 106 may be configured tocommunicate using wireless and/or wired communication circuitry. Thecommunication device 106 may be configured to transmit a request toattach to a first network node operating according to the first RAT andtransmit an indication that the wireless device is capable ofmaintaining substantially concurrent connections with the first networknode and a second network node that operates according to the secondRAT. The wireless device may also be configured transmit a request toattach to the second network node. The request may include an indicationthat the wireless device is capable of maintaining substantiallyconcurrent connections with the first and second network nodes. Further,the wireless device may be configured to receive an indication that dualconnectivity (DC) with the first and second network nodes has beenestablished.

As described herein, the communication device 106 may include hardwareand software components for implementing features for using multiplexingto perform transmissions according to multiple radio access technologiesin the same frequency carrier (e.g., and/or multiple frequencycarriers), as well as the various other techniques described herein. Theprocessor 302 of the communication device 106 may be configured toimplement part or all of the features described herein, e.g., byexecuting program instructions stored on a memory medium (e.g., anon-transitory computer-readable memory medium). Alternatively (or inaddition), processor 302 may be configured as a programmable hardwareelement, such as an FPGA (Field Programmable Gate Array), or as an ASIC(Application Specific Integrated Circuit). Alternatively (or inaddition) the processor 302 of the communication device 106, inconjunction with one or more of the other components 300, 304, 306, 310,320, 329, 330, 340, 345, 350, 360 may be configured to implement part orall of the features described herein.

In addition, as described herein, processor 302 may include one or moreprocessing elements. Thus, processor 302 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof processor 302. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processor(s) 302.

Further, as described herein, cellular communication circuitry 330 andshort range wireless communication circuitry 329 may each include one ormore processing elements and/or processors. In other words, one or moreprocessing elements or processors may be included in cellularcommunication circuitry 330 and, similarly, one or more processingelements or processors may be included in short range wirelesscommunication circuitry 329. Thus, cellular communication circuitry 330may include one or more integrated circuits (ICs) that are configured toperform the functions of cellular communication circuitry 330. Inaddition, each integrated circuit may include circuitry (e.g., firstcircuitry, second circuitry, etc.) configured to perform the functionsof cellular communication circuitry 330. Similarly, the short rangewireless communication circuitry 329 may include one or more ICs thatare configured to perform the functions of short range wirelesscommunication circuitry 329. In addition, each integrated circuit mayinclude circuitry (e.g., first circuitry, second circuitry, etc.)configured to perform the functions of short range wirelesscommunication circuitry 329.

FIG. 4—Block Diagram of a Base Station

FIG. 4 illustrates an example block diagram of a base station 102,according to some embodiments. It is noted that the base station of FIG.4 is merely one example of a possible base station. As shown, the basestation 102 may include processor(s) 404 which may execute programinstructions for the base station 102. The processor(s) 404 may also becoupled to memory management unit (MMU) 440, which may be configured toreceive addresses from the processor(s) 404 and translate thoseaddresses to locations in memory (e.g., memory 460 and read only memory(ROM) 450) or to other circuits or devices.

The base station 102 may include at least one network port 470. Thenetwork port 470 may be configured to couple to a telephone network andprovide a plurality of devices, such as UE devices 106, access to thetelephone network as described above in FIGS. 1 and 2.

The network port 470 (or an additional network port) may also oralternatively be configured to couple to a cellular network, e.g., acore network of a cellular service provider. The core network mayprovide mobility related services and/or other services to a pluralityof devices, such as UE devices 106. In some cases, the network port 470may couple to a telephone network via the core network, and/or the corenetwork may provide a telephone network (e.g., among other UE devicesserviced by the cellular service provider).

In some embodiments, base station 102 may be a next generation basestation, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In suchembodiments, base station 102 may be connected to a legacy evolvedpacket core (EPC) network and/or to a NR core (NRC) network. Inaddition, base station 102 may be considered a 5G NR cell and mayinclude one or more transition and reception points (TRPs). In addition,a UE capable of operating according to 5G NR may be connected to one ormore TRPs within one or more gNB s.

The base station 102 may include at least one antenna 434, and possiblymultiple antennas. The radio 430 and at least one antenna 434 may beconfigured to operate as a wireless transceiver and may be furtherconfigured to communicate with UE devices 106. The antenna 434 maycommunicate with the radio 430 via communication chain 432.Communication chain 432 may be a receive chain, a transmit chain orboth. The radio 430 may be configured to communicate via variouswireless communication standards, including, but not limited to, 5G NR,LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

The base station 102 may be configured to communicate wirelessly usingmultiple wireless communication standards. In some instances, the basestation 102 may include multiple radios, which may enable the basestation 102 to communicate according to multiple wireless communicationtechnologies. For example, as one possibility, the base station 102 mayinclude an LTE radio for performing communication according to LTE aswell as a 5G NR radio for performing communication according to 5G NR.In such a case, the base station 102 may be capable of operating as bothan LTE base station and a 5G NR base station. As another possibility,the base station 102 may include a multi-mode radio which is capable ofperforming communications according to any of multiple wirelesscommunication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTEand UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

As described further subsequently herein, the BS 102 may includehardware and software components for implementing or supportingimplementation of features described herein. The processor 404 of thebase station 102 may be configured to implement or supportimplementation of part or all of the methods described herein, e.g., byexecuting program instructions stored on a memory medium (e.g., anon-transitory computer-readable memory medium). Alternatively, theprocessor 404 may be configured as a programmable hardware element, suchas an FPGA (Field Programmable Gate Array), or as an ASIC (ApplicationSpecific Integrated Circuit), or a combination thereof. Alternatively(or in addition) the processor 404 of the BS 102, in conjunction withone or more of the other components 430, 432, 434, 440, 450, 460, 470may be configured to implement or support implementation of part or allof the features described herein.

In addition, as described herein, processor(s) 404 may include one ormore processing elements. Thus, processor(s) 404 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof processor(s) 404. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processor(s) 404.

Further, as described herein, radio 430 may include one or moreprocessing elements. Thus, radio 430 may include one or more integratedcircuits (ICs) that are configured to perform the functions of radio430. In addition, each integrated circuit may include circuitry (e.g.,first circuitry, second circuitry, etc.) configured to perform thefunctions of radio 430.

FIG. 5—Block Diagram of Cellular Communication Circuitry

FIG. 5 illustrates an example simplified block diagram of cellularcommunication circuitry, according to some embodiments. It is noted thatthe block diagram of the cellular communication circuitry of FIG. 5 isonly one example of a possible cellular communication circuit; othercircuits, such as circuits including or coupled to sufficient antennasfor different RATs to perform uplink activities using separate antennas,are also possible. According to embodiments, cellular communicationcircuitry 330 may be included in a communication device, such ascommunication device 106 described above. As noted above, communicationdevice 106 may be a user equipment (UE) device, a mobile device ormobile station, a wireless device or wireless station, a desktopcomputer or computing device, a mobile computing device (e.g., a laptop,notebook, or portable computing device), a tablet and/or a combinationof devices, among other devices.

The cellular communication circuitry 330 may couple (e.g.,communicatively; directly or indirectly) to one or more antennas, suchas antennas 335 a-b and 336 as shown (in FIG. 3). In some embodiments,cellular communication circuitry 330 may include dedicated receivechains (including and/or coupled to, e.g., communicatively, directly orindirectly, dedicated processors and/or radios) for multiple RATs (e.g.,a first receive chain for LTE and a second receive chain for 5G NR). Forexample, as shown in FIG. 5, cellular communication circuitry 330 mayinclude a modem 510 and a modem 520. Modem 510 may be configured forcommunications according to a first RAT, e.g., such as LTE or LTE-A, andmodem 520 may be configured for communications according to a secondRAT, e.g., such as 5G NR.

As shown, modem 510 may include one or more processors 512 and a memory516 in communication with processors 512. Modem 510 may be incommunication with a radio frequency (RF) front end 530. RF front end530 may include circuitry for transmitting and receiving radio signals.For example, RF front end 530 may include receive circuitry (RX) 532 andtransmit circuitry (TX) 534. In some embodiments, receive circuitry 532may be in communication with downlink (DL) front end 550, which mayinclude circuitry for receiving radio signals via antenna 335 a.

Similarly, modem 520 may include one or more processors 522 and a memory526 in communication with processors 522. Modem 520 may be incommunication with an RF front end 540. RF front end 540 may includecircuitry for transmitting and receiving radio signals. For example, RFfront end 540 may include receive circuitry 542 and transmit circuitry544. In some embodiments, receive circuitry 542 may be in communicationwith DL front end 560, which may include circuitry for receiving radiosignals via antenna 335 b.

In some embodiments, a switch (e.g., and/or combiner, multiplexer, etc.)570 may couple transmit circuitry 534 to uplink (UL) front end 572. Inaddition, switch 570 may couple transmit circuitry 544 to UL front end572. UL front end 572 may include circuitry for transmitting radiosignals via antenna 336. Thus, when cellular communication circuitry 330receives instructions to transmit according to the first RAT (e.g., assupported via modem 510), switch 570 may be switched to a first statethat allows modem 510 to transmit signals according to the first RAT(e.g., via a transmit chain that includes transmit circuitry 534 and ULfront end 572). Similarly, when cellular communication circuitry 330receives instructions to transmit according to the second RAT (e.g., assupported via modem 520), switch 570 may be switched to a second statethat allows modem 520 to transmit signals according to the second RAT(e.g., via a transmit chain that includes transmit circuitry 544 and ULfront end 572).

In some embodiments, modem 510 and modem 520 may be configured totransmit at the same time, receive at the same time, and/or transmit andreceive at the same time. Thus, when cellular communication circuitry330 receives instructions to transmit according to both the first RAT(e.g., as supported via modem 510) and the second RAT (e.g., assupported via modem 520), combiner 570 may be switched to a third statethat allows modems 510 and 520 to transmit signals according to thefirst and second RATs (e.g., via a transmit circuitry 534 and 544 and ULfront end 572). In other words, the modems may coordinate communicationactivity, and each may perform transmit and/or receive functions at anytime, as desired.

In some embodiments, the cellular communication circuitry 330 may beconfigured to transmit, via the first modem while the switch is in thefirst state, a request to attach to a first network node operatingaccording to the first RAT and transmit, via the first modem while theswitch is in a first state, an indication that the wireless device iscapable of maintaining substantially concurrent connections with thefirst network node and a second network node that operates according tothe second RAT. The wireless device may also be configured transmit, viathe second radio while the switch is in a second state, a request toattach to the second network node. The request may include an indicationthat the wireless device is capable of maintaining substantiallyconcurrent connections with the first and second network nodes. Further,the wireless device may be configured to receive, via the first radio,an indication that dual connectivity with the first and second networknodes has been established.

As described herein, the modem 510 may include hardware and softwarecomponents for implementing features for using multiplexing to performtransmissions according to multiple radio access technologies in thesame frequency carrier, as well as the various other techniquesdescribed herein. The processors 512 may be configured to implement partor all of the features described herein, e.g., by executing programinstructions stored on a memory medium (e.g., a non-transitorycomputer-readable memory medium). Alternatively (or in addition),processor 512 may be configured as a programmable hardware element, suchas an FPGA (Field Programmable Gate Array), or as an ASIC (ApplicationSpecific Integrated Circuit). Alternatively (or in addition) theprocessor 512, in conjunction with one or more of the other components530, 532, 534, 550, 570, 572, 335 and 336 may be configured to implementpart or all of the features described herein.

In some embodiments, processor(s) 512, 522, etc. may be configured toimplement or support implementation of part or all of the methodsdescribed herein, e.g., by executing program instructions stored on amemory medium (e.g., a non-transitory computer-readable memory medium).Alternatively, the processor(s) 512, 522, etc. may be configured as aprogrammable hardware element, such as an FPGA, or as an ASIC, or acombination thereof. In addition, as described herein, processor(s) 512,522, etc. may include one or more processing elements. Thus,processor(s) 512, 522, etc. may include one or more integrated circuits(ICs) that are configured to perform the functions of processor(s) 512,522, etc. In addition, each integrated circuit may include circuitry(e.g., first circuitry, second circuitry, etc.) configured to performthe functions of processor(s) 512, 522, etc.

As described herein, the modem 520 may include hardware and softwarecomponents for implementing features for using multiplexing to performtransmissions according to multiple radio access technologies in thesame frequency carrier, as well as the various other techniquesdescribed herein. The processors 522 may be configured to implement partor all of the features described herein, e.g., by executing programinstructions stored on a memory medium (e.g., a non-transitorycomputer-readable memory medium). Alternatively (or in addition),processor 522 may be configured as a programmable hardware element, suchas an FPGA (Field Programmable Gate Array), or as an ASIC (ApplicationSpecific Integrated Circuit). Alternatively (or in addition) theprocessor 522, in conjunction with one or more of the other components540, 542, 544, 550, 570, 572, 335 and 336 may be configured to implementpart or all of the features described herein.

FIGS. 6-7—5G NR Architecture

In some implementations, fifth generation (5G) wireless communicationwill initially be deployed concurrently with other wirelesscommunication standards (e.g., LTE). For example, whereas FIG. 6illustrates a possible standalone (SA) implementation of a nextgeneration core (NGC) network 606 and 5G NR base station (e.g., gNB604), dual connectivity between LTE and 5G new radio (5G NR or NR), suchas in accordance with the exemplary non-standalone (NSA) architectureillustrated in FIG. 7, has been specified as part of the initialdeployment of NR. Thus, as illustrated in FIG. 7, evolved packet core(EPC) network 600 may continue to communicate with current LTE basestations (e.g., eNB 602). In addition, eNB 602 may be in communicationwith a 5G NR base station (e.g., gNB 604) and may pass data between theEPC network 600 and gNB 604. In some instances, the gNB 604 may alsohave at least a user plane reference point with EPC network 600. Thus,EPC network 600 may be used (or reused) and gNB 604 may serve as extracapacity for UEs, e.g., for providing increased downlink throughput toUEs. In other words, LTE may be used for control plane signaling and NRmay be used for user plane signaling. Thus, LTE may be used to establishconnections to the network and NR may be used for data services. As willbe appreciated, numerous other non-standalone architecture variants arepossible.

FIGS. 8-9—Radio Capability Signaling

Modern wireless communication systems, e.g., cellular systems such as 5GNR, may allow for a UE (e.g., UE 106) and a base station (e.g., BS 102)to exchange various types of signals and data such as application dataand control information. One type of control information may be radioaccess capability signaling (RACS). RACS may indicate variousinformation about the capabilities of the UE, e.g., related toperforming communication on various frequencies or combinations offrequencies, beamforming capabilities, communicating using variousmultiple-in-multiple-out (MIMO) techniques, VoLTE enablement, eDRXsupport, FDD and/or TDD enablement, etc. RACS is described in varioustechnical standards, such as 3GPP TS 23.501 v16.1.0, clause 5.4.4.1a,titled UE radio capability signaling optimisation (RACS).

With the increase of the size of UE radio capabilities driven e.g. byadditional frequency bands and combinations thereof for E-UTRA and NR,an efficient approach to signal RACS information over the radiointerface and other network interfaces is beneficial. One approach maybe defined with RACS. RACS may work by assigning an identifier torepresent a set of UE radio capabilities. This identifier is called UEradio capability ID. A UE radio capability ID may be either UEmanufacturer assigned or PLMN-assigned, e.g., as specified in clause5.9.10 of 3GPP 23.501. The UE radio capability ID is an alternative tothe signaling of the radio capabilities container (e.g., transmittingdata on the UE radio capabilities) over the radio interface, within nextgeneration RAN (NG-RAN), from NG-RAN to E-UTRAN, from Access andMobility Management Function (AMF) to NG-RAN and between core network(CN) nodes supporting RACS. Note that a UE radio capability ID may beshared by any number of individual UEs which have the same radiocapabilities. Typically, the UEs that share a UE radio capability ID maybe of the same model.

A PLMN-assigned UE radio capability ID may be assigned to the UE usingthe UE Configuration Update procedure, or Registration Accept, e.g., asdefined in 3GPP TS 23.502, according to some embodiments. The UCMF (UEradio Capability Management Function) may store all UE radio capabilityID (e.g., PLMN-assigned and/or manufacturer-assigned) mappings in aPLMN. The UCMF may also assign PLMN-assigned UE radio capability IDs(see clause 6.2.21 of 3GPP TS 23.501).

3GPP TS 23.501 v16.1.0, clause 5.9.10 describes the UE radio capabilityID. The UE radio capability ID may be a short pointer with formatdefined in 3GPP TS 23.003 that may be used to uniquely identify a set ofUE Radio Capabilities. The UE radio capability ID may be assigned eitherby the serving PLMN or by the UE manufacturer, as follows:

Manufacturer-assigned: In some embodiments, the UE radio capability IDmay be assigned by the UE manufacturer in which case it may beaccompanied with the UE manufacturer information (e.g. TAC field in thePEI). In this case, the UE radio capability ID may uniquely identify aset of UE Radio Capabilities for this manufacturer, and together withthis UE manufacturer information may uniquely identify this set of UERadio Capabilities in any PLMN.

PLMN-assigned: In some embodiments, if a manufacturer-assigned UE radiocapability ID is not used by the UE or the serving network, or it is notrecognized by the serving PLMN UCMF, the UCMF may allocate UE radiocapability IDs for the UE. UE radio capability IDs may correspond todifferent sets of UE radio capabilities that the PLMN may receive fromthe UE (e.g., or other similar UEs), e.g., at different times. In thiscase, the UE radio capability IDs the UE receives are applicable to theserving PLMN and may uniquely identify the corresponding sets of UERadio Capabilities in this PLMN.

The type of UE radio capability ID (e.g., manufacturer-assigned orPLMN-assigned) may be distinguished when a UE radio capability ID issignaled.

3GPP TS 23.501 v16.1.0, clause 6.2.21 describes aspects of the UE radioCapability Management Function (UCMF). The UCMF may be used for storageof dictionary entries corresponding to PLMN-assigned and/orManufacturer-assigned UE radio capability IDs. An AMF may subscribe withthe UCMF to obtain from the UCMF new values of UE radio capability IDthat the UCMF assigns for the purpose of caching them locally.Provisioning of Manufacturer-assigned UE radio capability ID entries inthe UCMF may be performed from an AF that interacts with the UCMF eitherdirectly or via the network exposure function (NEF) (or via NetworkManagement) using a procedure, e.g., as defined in 3GPP TS 23.502.

For PLMN-assigned UE radio capability ID, the UCMF may also be thefunction that assigns the UE radio capability ID values to the UE. EachPLMN-assigned UE radio capability ID may also be associated to the typeallocation code (TAC) and software version (SV) (e.g., software versionnumber (SVN)) of the UE model that it is related to. When an AMFrequests the UCMF to assign a UE radio capability ID for a set of UERadio Capabilities, the AMF may indicate the TAC and SV of the UE thatthe UE Radio Capabilities are related to.

Table 7.2.18-1 of 3GPP TS 23.501 v.16.1.0, reproduced below, illustratesnetwork function (NF) Services provided by UCMF.

Reference in Technical Service Name Description Specification 23.502Nucmf_Provisioning Allows the NF consumer to 5.2.18.2 provision adictionary entry in the UCMF consisting of a Manufacturer- assigned UEradio capability ID and the corresponding UE radio access capability.Nucmf_UECapabilityManagement Allows the NF consumer to resolve 5.2.18.3UE radio capability ID (either Manufacturer-assigned or PLMN- assigned)into the corresponding UE radio access capability. Allows the NFconsumer to obtain a PLMN-assigned UE radio capability ID for a specificUE radio access capability. Allows the NF consumer to subscribe orunsubscribe for notifications of UCMF dictionary entries. Allows the NFconsumer to be notified about creation and deletion of UCMF dictionaryentries.

FIG. 8 illustrates radio capability signaling architecture, according tosome embodiments. As shown, N55 may be the Reference point between AMFand the UCMF, N56 may be the Reference point between NEF and the UCMF,and N57 may be the reference point between AF and the UCMF.

FIG. 9 illustrates roaming architecture for RACS, according to someembodiments. As shown, a UE on a visited PLMN (VPLMN) may communicatewith the RAN of the VPLMN. Among various connections, an AMF of theVPLMN may communicate with a UCMF of the VPLMN and an AF of the UE'shome PLMN (HPLMN).

Table 5.2.18.1-1 of 3GPP TS 23.502 v.16.1.0, reproduced below,illustrates UCMF services, according to some embodiments.

Service Operation Example Service Name Operations Semantics Consumer(s)Nucmf_Provisioning Create Request/Response AF, NEF DeleteRequest/Response AF, NEF Nucmf_UECapabilityManagement ResolveRequest/Response AMF Assign Request/Response AMF SubscribeSubscribe/Notify AMF Unsubscribe Subscribe/Notify AMF NotifySubscribe/Notify AMF

Table 5.2.19.1-1 of 3GPP TS 23.502 v.16.1.0, reproduced below,illustrates AF services, according to some embodiments.

Service Operation Example Service Name Operations Semantics Consumer(s)Naf_EventExposure Subscribe Subscribe/Notify NEF, NWDAF Unsubscribe NEF,NWDAF Notify NEF, NWDAF

In order to be able to interpret the UE radio capability ID a NF or nodemay store a local copy of the mapping between the UE radio capability IDand its corresponding UE Radio Access Capabilities information, e.g., adictionary entry. When no mapping is available between a UE radiocapability ID and the corresponding UE radio capability information in aNetwork Function or node, this Network Function or node may retrievethis mapping from the UCMF and store it.

An AMF which supports RACS may store such UE radio capability ID mappingfor all the UEs that it serves that have a UE radio capability IDassigned (e.g., and possibly additional UEs, e.g., which may not becurrently served by the AMF). The NG-RAN may perform local caching ofthe UE Radio Access Capabilities for the UE radio capability IDs for theUEs it is serving, and potentially for other UE radio capability IDsaccording to suitable local policies. When the NG-RAN needs to retrievethe mapping of a UE radio capability ID to the corresponding UE radiocapability information, it may query the AMF using N2 signaling, e.g.,defined in Technical Specification 38.413. When the AMF needs toretrieve a (e.g., PLMN-assigned) UE radio capability ID for a UE fromthe UCMF, it may provide the UE Radio Capabilities Information for theUE. The UCMF may store the association of this IMEI/TAC and SV with thisUE radio capability ID. When the AMF retrieves the UE radio capabilityInformation associated to a UE radio capability ID it may provide the UEradio capability ID to UCMF, e.g., in order to obtain a mapping of a UEradio capability ID to the corresponding UE Radio Capabilitiesinformation.

FIGS. 10-12—New UE Radio Capability ID Format

As noted above, the existing UE radio capabilities identifier may useTAC and SVN, to uniquely identify the set of UE capabilities to thenetwork, e.g., as shown in FIG. 10, according to some embodiments. AnSVN update may not happen when the capabilities are updated viacustomization (e.g., a capability update, e.g., sometimes referred to ascarrier bundle or bundle update). An SVN update may happen when there isa change in the baseband build. Often, new features may be added in theUE for particular carrier via capability update such as VoLTEenablement, eDRX support, FDD and/or TDD enablement, etc. Addition ofsuch new features (e.g., and/or modification of existing features) maychanges the UE capabilities without a change in SVN. To meet thespecific carrier requirements, frequent addition of bands and carrieraggregation (CA) combos may be done by device manufacturers inbundle/capability update(s). This may lead to change in the UEcapabilities without change in SVN.

FIG. 11 is a flow diagram which illustrates exemplary aspects of using anew UE radio capability ID format which may be updated in response to acapability update. Aspects of the method of FIG. 11 may be implementedby a UE 106 in communication with a cellular network (e.g., via a BS102) and in further communication with a manufacturer server 109, asillustrated in and described with respect to the Figures, or moregenerally in conjunction with any of the computer circuitry, systems,devices, elements, or components shown in the Figures, among otherdevices, as desired. For example, a processor (or processors) of the UE(e.g., processor(s) 302, processor(s) associated with communicationcircuitry 329 or 330 such as processor(s) 512 and/or 522, etc.), basestation (e.g., processor(s) 404, or a processor associated with radio430 and/or communication chain 432, among various possibilities), ornetwork element (e.g., any component of NGC 606, EPC 600, etc.), ormanufacturer server 109 may cause the UE, base station, networkelement(s), and/or manufacturer server to perform some or all of theillustrated method elements. For example, a baseband processor orapplication processor of the UE may cause the UE to perform some or allof the illustrated method elements. Note that while at least someelements of the method are described in a manner relating to the use ofcommunication techniques and/or features associated with 3GPPspecification documents, such description is not intended to be limitingto the disclosure, and aspects of the method may be used in any suitablewireless communication system, as desired. In various embodiments, someof the elements of the methods shown may be performed concurrently, in adifferent order than shown, may be substituted for by other methodelements, or may be omitted. Additional method elements may also beperformed as desired. As shown, the method may operate as follows.

A manufacturer server 109 may receive an updated UE radio configuration,e.g., a capability update, e.g., from an engineering team of themanufacturer (1102), according to some embodiments. The capabilityupdate (e.g., updated radio configuration) may be related to performingcommunication on various frequencies or combinations of frequencies, CA,beamforming capabilities, MIMO, etc. The capability update may beassociated with a capability identifier (CI) or the manufacturer servermay create an associated CI. The capability update may not change asoftware version number.

The manufacturer server 109 may create a (e.g., manufacturer created) UEradio capability ID, e.g., based on a CI as TAC+SVN+CI (1104), accordingto some embodiments. Thus, for any change in the UE capability, e.g.,for a particular carrier or PLMN, an updated manufacturer radio UE radiocapability ID may be created, according to some embodiments. In otherwords, the CI field may include sufficient information (e.g., incombination with the TAC and SVN), to uniquely identify set of UEcapabilities, including to differentiate between the capabilities ofotherwise similar UEs with and without the update. The UE radiocapability ID may have the same SVN as a previous UE radio capabilityID, e.g., because the updated configuration may not change the SVN.

To create the “CI” field in a UE radio capability ID, a manufacturer mayuse the existing opcode of the header section format of section 4.1.1 ofRFC 1035, e.g., one or more of bits 3-15 indicated as reserved forfuture use, may be used.

In some scenarios, TAC and SV may not be sufficient to identify the setof UE capabilities. For every 1 million devices, TAC needs to beupdated. Thus, for a popular UE model, a different UE radio capabilityID may be reserved for the same set of radio capabilities due to changein TAC and SV. Additionally or alternatively, a different UE radiocapability ID may be used to replace TAC with a model ID. Model ID mayuniquely identify the UE model, e.g., iPhone XS. In some embodiments, amanufacturer-assigned or PLMN-assigned UE radio capability ID may becomposed of the following elements model ID, SVN, and CI. It will beappreciated that a model ID may implicitly or explicitly indicate thevendor/manufacturer of the UE. In other words, a vendor identificationmay be a subset of a model ID, e.g., a model ID may be useable todetermine a vendor/manufacturer. A model ID may be referred to as avendor ID.

The manufacturer server 109 may transmit the created UE radio capabilityID and/or associated capability information to one or more elements ofthe network 100, e.g., a UCMF (1106), according to some embodiments. Thenetwork element may create a dictionary entry for the UE radiocapability ID and capability information, or otherwise store the ID andassociated information locally. It will be appreciated that themanufacturer server 109 may provide to the UCMF and/or other networkelement(s) any relevant information about the UE radio capability ID andassociated information. For example, the manufacturer server may providea list of TACs for which a UE radio capability ID based on model ID mayapply.

The manufacturer server 109 may transmit (e.g., push) the capabilityupdate to (e.g., relevant) UEs on the network 100 (1108), according tosome embodiments. For example, the server may send the update to all UEson the network of a certain model (or models) to which the update istargeted. The update may be mandatory (e.g., forced) or it may beoptional (e.g., unforced). The server may also provide an indication ofthe UE radio capability ID, e.g., so that the UE's may use the ID infuture communications with the network and/or other networks.

FIGS. 12-16—Updating UE Radio Capability Via a Forced Update

UE radio capabilities may be updated using a forced update (e.g., whichall effected UEs must perform at once) or an unforced update (e.g.,which may be performed at the discretion of the individual UE and/oruser).

When there is a capability update including a radio capabilities change,many UEs may register at once with full radio capabilities, according tosome embodiments. This may lead to huge signaling overhead. Similarly,since many the UEs may register with full radio capabilities, this willlead to high load in AMF<->UCMF interface. Further, the capabilityupdate may not update the SVN, hence the (e.g., existing) UE radiocapability ID (e.g., TAC+SNR+SVN, model ID+SNR+SVN, TAC+SVN, or modelID+SVN, etc., as illustrated in FIG. 10) may not reflect the UEcapability update.

FIG. 12 is a flow diagram which illustrates exemplary aspects of aforced capability update, according to some embodiments. Aspects of themethod of FIG. 12 may be implemented by a UE 106 in communication with acellular network (e.g., via a BS 102) and in further communication witha manufacturer server 109, as illustrated in and described with respectto the Figures, or more generally in conjunction with any of thecomputer circuitry, systems, devices, elements, or components shown inthe Figures, among other devices, as desired. For example, a processor(or processors) of the UE (e.g., processor(s) 302, processor(s)associated with communication circuitry 329 or 330 such as processor(s)512 and/or 522, etc.), base station (e.g., processor(s) 404, or aprocessor associated with radio 430 and/or communication chain 432,among various possibilities), or network element (e.g., any component ofNGC 606, EPC 600, etc.), or manufacturer server 109 may cause the UE,base station, network element(s), and/or manufacturer server to performsome or all of the illustrated method elements. For example, a basebandprocessor or application processor of the UE may cause the UE to performsome or all of the illustrated method elements. Note that while at leastsome elements of the method are described in a manner relating to theuse of communication techniques and/or features associated with 3GPPspecification documents, such description is not intended to be limitingto the disclosure, and aspects of the method may be used in any suitablewireless communication system, as desired. In various embodiments, someof the elements of the methods shown may be performed concurrently, in adifferent order than shown, may be substituted for by other methodelements, or may be omitted. Additional method elements may also beperformed as desired. As shown, the method may operate as follows.

A manufacturer server 109 may receive an updated UE radio configuration,e.g., a capability update (e.g., as discussed above with respect to1102), according to some embodiments. The capability update may beassociated with a new manufacturer created UE radio capability IDidentifier (e.g., TAC+SVN+CI or model ID+SVN+CI as described withrespect to FIG. 11), according to some embodiments. The capabilityupdate may be associated with one or more manufacturer and/or PLMNcreated UE radio capability ID(s) according to prior formats (e.g., asin FIG. 10, e.g., not including CI), according to some embodiments.

The manufacturer server 109 may transmit information about thecapability update such as request for a dictionary entry for thecapability update (1304), according to some embodiments. For example,the server may transmit a request to one or more network elements andmay specify capabilities associated with the capability update and a(e.g., manufacturer-assigned) UE radio capability ID. For example, basedon such a request, an AF and/or UCMF may generate a new dictionary basedon the capability update and associated UE radio capability ID. Thedictionary entry may use a new manufacturer-assigned UE radio capabilityID or a new PLMN-assigned UE radio capability ID as the UE radiocapability ID, among various possibilities. Thus, the capability update(e.g., the capabilities of UEs that implement the update) and associatedUE radio capability ID may be stored on the network and accessible tovarious network elements. For example, some or all network nodes (e.g.,AMF, RAN) may be updated with new UE radio capability ID.

The manufacturer server 109 may receive confirmation from the network100 that the capability information, e.g., of the capability update isstored (1308), according to some embodiments. For example, once all thenodes are updated, this information is feedback to the manufacturerserver via an application function (AF).

The manufacturer server 109 may transmit the forced update to (e.g.,all) the relevant UEs with the new capability update and may alsoprovide the new UE radio capability ID (e.g., TAC+SVN+CI or modelID+SVN+CI) (1310), according to some embodiments. The forced update mayconfigure the UEs to implement the forced update, store the new UE radiocapability ID, and delete a previous UE radio capability ID. The forcedupdate maybe transmitted in response to the confirmation from thenetwork that the capability update is stored.

The UE(s) 106 and network 100 may implement the capability update andthe new UE radio capability ID (1312), according to some embodiments.For example, during baseband refresh, a UE may start using a newmanufacturer ID (e.g., TAC+SVN+CI or model ID+SVN+CI, e.g., associatedwith the capability update). For example, the UE and network maycommunicate according to the updated capability of the UE, e.g.,accounting for the capability update and using the new UE radiocapability ID.

FIG. 13 is a call flow diagram illustrating example aspects of themethods of FIG. 12, in the case of a manufacturer-assigned UE radiocapability ID according to some embodiments.

Prior to the illustrated aspects, a new UE capability information withthe corresponding UE radio capability ID may be created in AF by amanufacturer server 109. The AMF may be subscribed to UCMF, e.g., usingNucmf_UECapabilityManagement_Subscribe. Similarly, the RAN may besubscribed to AMF, e.g., using Namf_Communication_N2InfoSubscribe.

As shown, a manufacturer server 109 may send aNaf_EventExposure_Subscribe message to AF (1414). This step may serve toindicate to the AF to start a procedure to create a new UE radiocapability ID in all NFs. The UE radio capability ID may be amanufacturer-created ID.

The AF may send the new UE capability information (e.g., potentiallywith a corresponding manufacturer-assigned UE radio capability ID to theUCMF via N57 interface using Nucmf_Provisioning_Create_request (1416).Note that the AF may use the new manufacturer-assigned UE radiocapability ID as TAC+SVN+CI or model ID+SVN+CI.

The UCMF may create one or more new dictionary entries for the receivedUE capability information (1418). The dictionary entry may include thecorresponding manufacturer-assigned UE radio capability ID (e.g., basedon TAC+SVN+CI or model ID+SVN+CI, according to some embodiments). TheUCMF may maintain a list of TACs for which the PLMN has obtained (e.g.,manufacturer-assigned) UE radio capability IDs and may update the listas part of creating the new dictionary entry or entries.

The UCMF may provide the new UE radio capability ID to the AMF via N55interface, e.g., using Nucmf_UECapabilityManagement_Notify (Creation)(1420).

The AMF may forward the new UE radio capability ID to the RAN usingNamf_Communication_N2InfoNotify (1422).

The RAN may send an acknowledgement (ACK) to the AMF once the new UEradio capability ID is added to the RAN's local database, e.g., usingNamf_Communication_N2InfoNotify_ACK (1424).

The AMF may send an ACK to UCMF once the new UE radio capability ID isadded to its local database, e.g., usingNucmf_UECapabilityManagement_Notify_ACK (1426).

The UCMF may inform the AF that the new UE radio capability ID has beenupdated in all network entities (1428), e.g., usingNucmf_Provisioning_Create_response.

The AF may inform the manufacturer server that the network has receivedthe information about the capability update (1430). This acknowledgement(e.g., flag) of the update may be an indication for the manufacturerserver to push the forced capability update to all UEs with the new UEradio capability ID (e.g., TAC+SVN+CI or model ID+SVN+CI), e.g., usingNaf_EventExposure_Notify. The acknowledgment may confirm that multiple(e.g., all) relevant network entities have received the informationabout the capability update.

The manufacturer server may transmit the forced update (1432), e.g.,with 2 flags to UE(s). The flags may inform the UE to implement theforced capability update with new UE radio capability ID and to deletethe old UE radio capability ID.

The manufacturer server may send Naf_EventExposure_Unsubscribe to AF(1434). This step may serve to indicate to the AF to start a procedureto delete the old UE radio capability ID in all NFs. Accordingly, theUCMF, AMF, and RAN may transmit respective messages to trigger thedeletion of the old UE radio capability ID (1436, 1438, 1444). The UCMFmay send a delete response (1446).

Each UE 106 may delete the old ID (1440) and initiate a baseband refresh(1442) and perform registration with new UE radio capability ID (1448).The AMF may accept the registration (1450).

FIG. 14 is a call flow diagram illustrating exemplary aspects of themethods of FIG. 12, e.g., in the case of a PLMN-assigned UE radiocapability ID, according to some embodiments.

Prior to the illustrated aspects, a new UE capability information (e.g.,capability update) may be created in AF by manufacturer server 109, theAMF may subscribed to UCMF, e.g., usingNucmf_UECapabilityManagement_Subscribe, and the RAN may be subscribed toAMF, e.g., using Namf_Communication_N2InfoSubscribe.

The manufacturer server may send Naf_EventExposure_Subscribe to AF(1514). This step may indicate to the AF to start procedure to createnew UE radio capability ID in all NFs.

The AF may send the new UE capability information to the UCMF (1516) viaN57 interface, e.g., using Nucmf_Provisioning_Create_request.

The UCMF may create new dictionary entries for the received UEcapability information along with a corresponding manufacturer-assignedUE radio capability ID (e.g., if a manufacturer-assigned ID is provided)(1518).

The UCMF may assign a PLMN-assigned UE radio capability ID mapped to thenew dictionary entry (1520). The PLMN-assigned UE radio capability IDmay correspond to (e.g., be mapped to, but different from) themanufacturer-assigned UE radio capability ID.

The UCMF may forward the new PLMN assigned UE radio capability ID to theAMF (1521) via N55 interface, e.g., usingNucmf_UECapabilityManagement_Notify (Creation).

The AMF may forward the new PLMN-assigned UE radio capability ID to theRAN using Namf_Communication_N2InfoNotify (1522).

The RAN may send an ACK to AMF (1524), e.g., once new PLMN-assigned UEradio capability ID is updated, e.g., usingNamf_Communication_N2InfoNotify_ACK.

The AMF may send an ACK to UCMF (1526), e.g., once new PLMN-assigned UEradio capability ID is updated, e.g., usingNucmf_UECapabilityManagement_Notify_ACK.

The UCMF may inform the AF that the new PLMN-assigned UE radiocapability ID has been updated in network entities (1528), e.g., usingNucmf_Provisioning_Create_response.

The AF may inform the manufacturer server that the new PLMN-assigned UEradio capability ID has been updated in network entities (1530), e.g.,using Naf_EventExposure_Notify.

Accordingly, the manufacturer server may proceed to push the forcedcapability update to relevant UEs (1532). For example, the manufacturerserver may raise a flag to UE indicating “Forced CB Update”.

The manufacturer server may send Naf_EventExposure_Unsubscribe to AF(1532). This unsubscribe message may indicate to the AF to startprocedure to delete old UE radio capability ID in all NFs. The NFs maytransmit messages accordingly (1536, 1538, 1540, 1542).

Each UE 106 may perform the update, initiate a baseband refresh (1534)and perform registration with new UE radio capability ID (1544).

The AMF may assign the new (e.g., PLMN-assigned) UE radio capability IDto each UE, e.g., in a registration accept message in response to theregistration of each UE (1546). Further, the AMF may send a“Configuration Update Command” message to UE to delete the old UE radiocapability ID (1548), e.g., in response to the registration. The UE mayrespond with a configuration update complete (1550).

Exemplary additions and/or modifications to standards documents that maybe made in association with implementation of the methods of FIG. 12 aredescribed below.

A first addition may be made to clause 5.2.18.3.5 of 3GPP technicalspecification 23.502 to add that the Nucmf_UECapabilityManagement_Notifymessage sent from UCMF to AMF, should contain an information element(IE) (e.g., optional or required) mentioning an ACK may be sent inresponse. This ACK may be listed as an optional or required output.

A second addition may be made to clause 5.2.2.2.10 of 3GPP technicalspecification 23.502 to add that the Namf_Communication_N2InfoNotifymessage may contain “UE radio capability ID” in N2 Information. This maybe listed as a required input. Further, the correspondingNamf_Communication_N2InfoNotify message sent from AMF to RAN may containan IE (e.g., optional or required) mentioning an ACK may be sent inresponse to this Notify message. This ACK may be listed as an optionalor required output.

Table 5.2.2.1-1 of 3GPP TS 23.502 v.16.1.0, reproduced below, highlightsthe N2InfoNotify in a list of AMF services, according to someembodiments.

Operation Known Service Name Service Operations Semantic Consumer(s)Namf_Communication UEContextTransfer Request/Response Peer AMFCreateUEContext Request/Response Peer AMF ReleaseUEContextRequest/Response Peer AMF RegistrationCompleteNotify Subscribe/NotifyPeer AMF N1MessageNotify Subscribe/Notify SMF, SMSF, PCF, LMF, Peer AMFN1MessageSubscribe SMF, SMSF, PCF N1MessageUnSubscribe SMF, SMSF, PCFN1N2MessageTransfer Request/Response SMF, SMSF, PCF, LMFN1N2TransferFailureNotification Subscribe/Notify SMF, SMSF, PCF, LMFN2InfoSubscribe Subscribe/Notify NOTE 1 N2InfoUnSubscribe NOTE 1N2InfoNotify AMF, LMF EBIAssignment Request/Response SMFAMFStatusChangeSubscribe Subscribe/Notify SMF, PCF, NEF, SMSF, UDMAMFStatusChangeUnSubscribe Subscribe/Notify SMF, PCF, NEF, SMSF, UDMAMFStatusChangeNotify Subscribe/Notify SMF, PCF, NEF, SMSF, UDMNamf_EventExposure Subscribe Subscribe/Notify NEF, SMF, UDM UnsubscribeSubscribe/Notify NEF, SMF, UDM Notify Subscribe/Notify NEF, SMF, UDMNamf_MT EnableUEReachability Request/Response SMSFProvideDomainSelectionInfo Request/Response UDM Namf_LocationProvidePositioningInfo Request/Response GMLC EventNotifySubscribe/Notify GMLC ProvideLocationInfo Request/Response UDMCancelLocation Request/Response GMLC NOTE 1: In this Release of thespecification no known consumer is identified to use this serviceoperation.

A third addition may be made to clause 5.2.19.2.4 of 3GPP TS 23.502 toadd that a Naf_EventExposure_Notify message sent from AF to amanufacturer server 109, may contain an optional IE indication “Flag toupdate all UEs” or add an additional “entry” to “Event SpecificParameter List”. Thus, a flag to update all UEs (e.g., to provide thecapability update to UEs as the network has been updated with new IDinformation and dictionary entry corresponding to the capability update)may be listed as an optional (e.g., or required) input.

A fourth addition may be made to clause 6.5.3 of 3GPP TS 23.743 to addthat a configuration update command (e.g., from AMF to UE) shouldinclude an IE to delete any old PLMN ID. FIG. 15 illustrates UEregistration followed by a retrieval of UE capabilities, according tosome embodiments. FIG. 16 illustrates assignment of a new UE radiocapability ID, according to some embodiments. As noted above, theconfiguration update command may be modified (e.g., relative to existingspecifications) to include an IE to cause the UE to delete a previousPLMN ID (e.g., or multiple previous PLMN IDs).

FIGS. 17-18—Updating UE Radio Capability Via an Unforced Update

As noted above, UE radio capabilities may be updated using an unforcedupdate (e.g., which may be performed at the discretion of the individualUE and/or user). For example, these unforced capability updates may bestored in the UE implemented only when the user initiates the update(e.g., by going to General→Settings→About, according to someembodiments).

For a same manufacturer-assigned UE radio capability ID (e.g., TAC+SVNor model ID+SVN), a network may maintain two different PLMN IDs based onthe UE capability information, according to some embodiments. Thedifference in UE capability information may be due to different versionsof capability updates on different UEs (e.g., a first UE may haveimplemented a recent capability update while a second UE has not,accordingly the two UEs may have different capabilities, but a same UEradio capability ID based on TAC and SVN or model ID and SVN). In otherwords, there could be a scenario where UE capability between the samehardware and same location (e.g., and same PLMN) could differ due todifferent capability update versions. Thus, the PLMN may maintain twodifferent PLMN-assigned IDs for the same manufacturer-assigned ID

FIG. 17 is a flow diagram which illustrates exemplary aspects of anunforced capability update, according to some embodiments. Aspects ofthe method of FIG. 17 may be implemented by a cellular network (e.g.,including CN elements such as an AMF, UCMF, etc. and a RAN including aBS 102) in communication with a UE 106 and in further communication witha manufacturer server 109, as illustrated in and described with respectto the Figures, or more generally in conjunction with any of thecomputer circuitry, systems, devices, elements, or components shown inthe Figures, among other devices, as desired. For example, a processor(or processors) of the UE (e.g., processor(s) 302, processor(s)associated with communication circuitry 329 or 330 such as processor(s)512 and/or 522, etc.), base station (e.g., processor(s) 404, or aprocessor associated with radio 430 and/or communication chain 432,among various possibilities), or network element (e.g., any component ofNGC 606, EPC 600, etc.), or manufacturer server 109 may cause the UE,base station, network element(s), and/or manufacturer server to performsome or all of the illustrated method elements. For example, a basebandprocessor or application processor of the UE may cause the UE to performsome or all of the illustrated method elements. Note that while at leastsome elements of the method are described in a manner relating to theuse of communication techniques and/or features associated with 3GPPspecification documents, such description is not intended to be limitingto the disclosure, and aspects of the method may be used in any suitablewireless communication system, as desired. In various embodiments, someof the elements of the methods shown may be performed concurrently, in adifferent order than shown, may be substituted for by other methodelements, or may be omitted. Additional method elements may also beperformed as desired. As shown, the method may operate as follows.

The network 100 may receive a registration request from a UE 106 (e.g.,or multiple requests from multiple UEs) (1802), according to someembodiments. The registration request may include a UE radio capabilityID or may include information about the UE's radio capabilities. Forexample, a first plurality of UEs (e.g., of a particular model) mayregister with the network.

The network 100 may determine an initial UE radio capability ID for theUE(s) 106 (1804), according to some embodiments. The initial UE radiocapability ID may be PLMN-assigned or may be manufacturer-assigned. Theinitial UE radio capability ID may include information about acapability update (e.g., the ID may enable the network to distinguishbetween similar UEs which have and have not implemented a particularcapability update) or the UE radio capability ID may not include suchinformation.

The network 100 may create a new UE radio capability ID (1806),according to some embodiments. The new UE radio capability ID may becreated in response to a request for a new UE radio capability IDreceived from a manufacturer server 109. For example, the request may beassociated with an unforced capability update that the manufacturerserver 109 will soon release for (e.g., push out to) UE(s) 106, e.g., ofthe particular model. Such a request may provide information about thecapabilities of UEs that implement the capability update.

The network 100 may transmit a capability update (e.g., associated withthe new UE radio capability ID) to the UE(s) 106 (1808), according tosome embodiments. For example, the manufacturer server 109 may providethe capability update to the UEs via the CN and RAN of the network 100.For example, the network may send the capability update to all UEs ofthe particular model registered with the network.

The network 100 may receive an updated registration request from a UE106 (e.g., or multiple requests from multiple UEs) (1810), according tosome embodiments. The registration request may include the new UE radiocapability ID. Accordingly, the network may recognize that are-registering UE has implemented the capability update and may updatethe registration of the UE (e.g., including the stored UE radiocapability ID for the UE(s)) accordingly. For example, a subset of thefirst plurality of UEs may re-register with the new UE radio capabilityID.

The network 100 may maintain distinct UE radio capability IDs for theUEs which have and have not implemented the update (1812), according tosome embodiments. For example, the network may associate the new UEradio capability ID with the subset of the first plurality of UEs thathave implemented the capability update and may associate the initial UEradio capability ID with UEs which have not implemented the capabilityupdate. Thus, the network may communicate with UEs of the same modelusing different capabilities according to the different UE radiocapability IDs. It will be appreciated that over time additional UEs mayimplement the update and accordingly may re-register with the new UEradio capability ID.

FIG. 18 illustrates an example message flow according to someembodiments of the method of FIG. 17. For example, a new UE model (e.g.,iPhone XS) may be launched in a market (e.g., region). An AF may requestthe UCMF to create a new dictionary entry for this model (e.g., a firstmanufacturer-assigned UE radio capability ID and UE capabilityinformation may be shared). Accordingly, the UCMF may create a firstdictionary entry for this UE model. Alternatively, the AF may only sharethe UE capability information to the UCMF. Accordingly, the UCMF maycreate a new dictionary entry and assign a first PLMN-assigned UE radiocapability ID.

As illustrated in FIG. 18, UEs (e.g., of the new model, e.g., with aninitial bundle/capability version ‘x’) may be powered up and may sendregistration request to AMF. The registration request may include a UEradio capability ID, e.g., manufacturer-assigned. The AMF may requestthe UCMF to create a dictionary entry and assign the first PLMN-assignedUE radio capability ID to all the registering UEs. The AMF may acceptthe registration of the UEs. In some networks where PLMN-assigned UEradio capability ID is not supported, AMF and UCMF may continue to usemanufacturer-assigned UE radio capability ID.

In response to a request from the manufacturer server 109, the AF maysignal the UCMF to create a second new dictionary entry for same UEmodel but with updated “UE capability information”, e.g., in preparationfor an unforced capability update. In response, the UCMF may create asecond new dictionary entry and notify the AMF. Thus, two UE radiocapability IDs may be maintained by the UCMF for the new UE model, e.g.,a first UE radio capability ID for UEs that have not implemented theupdate and a second UE radio capability ID for the UEs that haveimplemented the update. In some embodiments, the two UE radio capabilityIDs may be PLMN-assigned IDs that correspond to a samemanufacturer-assigned ID. In some embodiments, both UE radio capabilityIDs may be manufacturer-assigned. In some embodiments, the UCMF mayprovide a new PLMN-assigned UE radio capability ID to the manufacturerserver, e.g., for the manufacturer server to provide to UEs along withthe capability update.

The manufacturer server may push the capability update to all UEs of thenew model. In some embodiments, the manufacturer server may indicate aUE radio capability ID (e.g., manufacturer-assigned or PLMN-assigned)associated with the capability update version “y”.

A subset of the UEs may update to the new bundle/capability version “y”.The UEs which have updated to bundle/capability version ‘y’ may performa baseband reset and may transmit a new registration request to AMF.

In some embodiments, the new registration request may be sent with same(e.g., first) manufacturer-assigned UE radio capability ID, but with newUE capability information. Accordingly, the AMF may retrieve thecorresponding (e.g., second) PLMN-assigned UE radio capability ID (e.g.,which may correspond to bundle/capability version “y”) from the UCMF andmay provide the second PLMN-assigned UE radio capability ID to the UE ina registration accept message.

In some embodiments, the new registration request may be sent with asecond UE radio capability ID (e.g., which may correspond tobundle/capability version “y”). The second UE radio capability ID may bemanufacturer-assigned or PLMN-assigned.

The network may maintain two UE radio capability IDs for same UE modelat the same location, only to be differentiated by UE capabilityinformation. For example, the network may maintain both the first andsecond UE radio capability IDs and use them for UEs which, respectively,have not and have implemented the update.

FIGS. 19-23—Dynamic UE Radio Capability ID Switch

From time to time, a UE may need to change (e.g., reduce or expand) itscapabilities. For example, in response to various thermal and/or batteryconditions (e.g., temperature of one or more components of the UE abovea relevant thermal threshold or thresholds, battery level below abattery threshold, etc.), a UE may operate using a reduced set ofcapabilities for a period of time (e.g., until the condition(s) that ledto the reduced capability change(s), until a timer expires, etc.).Accordingly, a UE may have multiple possible sets of capabilities. Thesesets of capabilities may be associated with different UE radiocapability IDs. For example, a UE would may maintain a set of UE radiocapability IDs for various capabilities including: one ID each fordifferent services like broadband, reduced version of broadband in caseof thermal or low power scenarios, internet of things (IoT), machinetype communication (MTC), ultra-reliable low latency communication(uRLLC), etc.

For example, a PLMN may decide to operate based on manufacturer-assignedUE radio capability ID for a particular type of UE (e.g. based on TACand/or SV). For a particular set of UE radio capability IDs that may beassumed to operate based on UE manufacturer-assigned UE radio capabilityID, the AMF may indicate to UEs to delete the PLMN-assigned UE radiocapability ID. A UE that receives an indication to delete thePLMN-assigned UE radio capability ID in the Registration Accept messageor UE configuration update command message may delete any PLMN-assignedUE radio capability IDs for this PLMN. The UE may then proceed toregister with the manufacturer assigned UE radio capability ID that isapplicable to the current UE radio configuration (e.g., currentcapability). The interaction between UCMF and AMF in order to switch tooperate based on manufacturer-assigned UE radio capability ID for aparticular type of UE is considered for future study in TS 23.501 v.16.2.0. In some embodiments, at any given time at most one UE radiocapability ID is stored in the UE context in CN and RAN.

In some embodiments, during the initial registration procedure the UEmay send a plurality of UE radio capability IDs to the network, e.g., inorder to inform the network of various IDs that the UE may use undervarious conditions. Such IDs may be used on a temporary basis (e.g.,based on conditions), and may be described as temporary IDs. The UE mayalso provide information about the meaning of each ID, e.g., describethe capabilities associated with each ID. For example, the UE mayprovide one or more UE radio capability IDs similar to the following,among various possibilities:

ID 1: Full configuration with all features enabled;

ID 2: Reduce data throughput capabilities considering battery/powerlevels;

ID 3: Restricted set of UE capability (e.g., lower maximum bandwidth,lower/fewer CA combinations, restricted MIMO options (e.g., no 4×4MIMO), etc.) for thermal or low power conditions;

ID 4: Low latency mode of operation (uRLLC, V2X, etc.);

ID 6: IoT mode of operation; and/or

ID 7: Any other capabilities addition/restriction.

In some embodiments, using such a list of UE radio capability IDs mayresult in a computational challenge for the network. For example, everytime AMF initiates the “Assign” or “Resolve” procedure, the UCMF maystream through its (e.g., potentially huge) dictionary/database and findthe exact matching UE radio capability ID or UE capability informationrespectively. Assuming each UE model maintains 7 different UE capabilityinformation in the UCMF, and considering the amount of UE modelsreleased in the market (e.g., 1000 per year), a large number (e.g.,7000) dictionary entries may be added to the dictionary/database eachyear. Accordingly, for temporary situations, it may be inefficient touse UCMF resources (e.g., dictionary entry and/or PLMN-ID) and theAMF<->UCMF interface for storing and signaling use of such IDs.

FIG. 19 is a flow diagram which illustrates exemplary aspects of dynamicswitching of UE radio capability IDs, according to some embodiments.Aspects of the method of FIG. 19 may be implemented by a cellularnetwork (e.g., including CN elements such as an AMF, UCMF, etc. and aRAN including a BS 102) in communication with a UE 106 and in furthercommunication with a manufacturer server 109, as illustrated in anddescribed with respect to the Figures, or more generally in conjunctionwith any of the computer circuitry, systems, devices, elements, orcomponents shown in the Figures, among other devices, as desired. Forexample, a processor (or processors) of the UE (e.g., processor(s) 302,processor(s) associated with communication circuitry 329 or 330 such asprocessor(s) 512 and/or 522, etc.), base station (e.g., processor(s)404, or a processor associated with radio 430 and/or communication chain432, among various possibilities), or network element (e.g., anycomponent of NGC 606, EPC 600, etc.), or manufacturer server 109 maycause the UE, base station, network element(s), and/or manufacturerserver to perform some or all of the illustrated method elements. Forexample, a baseband processor or application processor of the UE maycause the UE to perform some or all of the illustrated method elements.Note that while at least some elements of the method are described in amanner relating to the use of communication techniques and/or featuresassociated with 3GPP specification documents, such description is notintended to be limiting to the disclosure, and aspects of the method maybe used in any suitable wireless communication system, as desired. Invarious embodiments, some of the elements of the methods shown may beperformed concurrently, in a different order than shown, may besubstituted for by other method elements, or may be omitted. Additionalmethod elements may also be performed as desired. As shown, the methodmay operate as follows.

A UE 106 may register with a network 100 (2002), according to someembodiments. The registration may be an initial registration. The UE mayprovide full UE capability information or a manufacturer-assigned UEradio capability ID. The network may assign a PLMN-assigned UE radiocapability ID. The UE may initially operate using its full capability,e.g., according to the initial UE radio capability ID.

The UE 106 may determine to operate at a reduced capability on atemporary basis (2004), according to some embodiments. Thisdetermination may be based on one or more conditions present at thedevice such as temperature, battery level, etc. For example, in responseto detecting a changed condition, the UE may determine to reduce itscapability for a period of time (e.g., 10 minutes, among variouspossibilities). For example, in response to a temperature of one or morecomponents of the UE reaching a thermal threshold (or thresholds) the UEmay determine to reduce its transmit power for a period of time to allowthe component to cool down. For example, when a UE hits a thermalcondition (e.g., a temporary situation, e.g., 10 mins), the UE maydecide to restrict its UE capability information to save power (e.g.,restrict number of DL/UL component carriers (CC), disable 4×4 MIMO,etc.) for a period of time. The duration of the period of time may bepre-defined (e.g., using a timer, e.g., 10 minutes) and/or may bedetermined dynamically (e.g., based on improvement in measurements ofthe temperature, battery level, or other condition(s) that led to thereduction in capability).

The UE 106 may re-register or otherwise update its registration with thenetwork 100 (2006), according to some embodiments. For example, the UEmay re-register in response to the determination to operate at thereduced capability. The re-registration may allow the UE to inform thenetwork of the reduced capability.

For example, the UE may send an updated registration request to AMF withthe following IEs: temporary UE radio capability ID and restricted UEradio capability information (e.g., a description of the temporarilyrestricted capability). The temporary UE radio capability ID may thus beassociated with the temporarily restricted capability in the network.

In some embodiments, the registration request may further include an IEdescribing a validity period (e.g., a timer for the length of thecapability restriction).

The network (e.g., AMF) may receive the updated registration request.

In some embodiments, the AMF may inform the UCMF to create a dictionaryentry in its dictionary, but not to assign a PLMN-assigned UE radiocapability ID. This may avoid/reduce excessive use of PLMN-assigned UEradio capability IDs.

In some embodiments, the AMF may create a local cache and maintains thissession with the UE without informing the UCMF to create a dictionaryentry. This may avoid/reduce the use of dictionary entries andPLMN-assigned UE radio capability IDs.

The AMF may send, and the UE may receive a registration accept. Thus,the UE may continue the session with the temporary UE radio capabilityID and operating with the temporarily reduced capability.

The UE 106 may revert to the initial UE radio capability ID (2008),according to some embodiments. For example, in response to adetermination that conditions (e.g., thermal conditions, battery level,etc.) have improved or in response to determination that the validityperiod timer expires, the UE revert back to the initial UE radiocapability ID.

In some embodiments, this reversion may be accomplished by a furtherregistration procedure (e.g., re-registration). For example, the UE mayre-register using the initial UE radio capability ID. Such are-registration may signal to the network that the UE may now operate atfull capability, e.g., as described by the initial UE radio capabilityID.

In some embodiments, this reversion may occur automatically, e.g., atthe expiration of a validity timer associated with the temporarycapability reduction. For example, if such a timer is initiated when thetemporary capability reduction begins, then no further signaling may berequired to revert to full capability and the initial UE radiocapability ID. However, it should be noted that if the validity periodtimer expires and the (e.g., thermal) conditions do not improve, the UEmay extend the validity timer. For example, a new IE may be defined forany message from UE to AMF, e.g., to extend the duration of the validitytimer. Further, the UE may initiate a re-registration (e.g., at or priorto expiration of the timer) in order to re-start the validity (e.g.,with the same duration or a different duration) in order to allow moretime for conditions to improve prior to reverting to full capability.Still further, the UE may initiate reversion prior to expiration of thetimer in response to a determination that conditions at the UE haveimproved, e.g., the reversion may not be based on expiration of thetimer.

FIGS. 20 and 21 are call flow diagrams illustrating example aspects ofthe method of FIG. 19, according to some embodiments. FIG. 20illustrates embodiments in which the AMF informs the UCMF of a UE'sreduced capability and FIG. 21 illustrates embodiments in which the AMFcaches a temporary ID for the UE locally.

As shown in FIG. 20, a UE 106 (e.g., which supports RACS) may send thefull UE capability information to the AMF during an initial registrationprocedure (2110).

The AMF may signal the UCMF to create a new dictionary entry in itsdictionary and store the UE capability information via theNucmf_Provisioning (Create) service message (2112). In response, theUCMF may store the association in its dictionary (2114, 2116) and maysend back a newly created PLMN-assigned UE radio capability ID (e.g., IDA) to AMF via the Nucmf_UECapabilityManagement (Assign) service (2118).

The AMF may send a registration accept message to the UE, e.g.,including the PLMN-assigned ID “A” (2120).

The UE may determine to operate at a reduced capability, e.g., inresponse to reaching a thermal condition (e.g., temperature reaching athreshold) (2122). In response, the UE may send a registration requestto AMF, e.g., with an NG-RAN radio capability update (RCU) flag enabled,e.g., in a “5GS update type” IE (2124). Note that 5GS Update Type may bethe IE specified in 3GPP 24.501 and that 5GS may refer to 5G System(e.g., similar to EPS for LTE). This registration message may inform thenetwork that UE wants to change its UE radio capability ID and/orcapability.

In response to the updated registration request, the AMF may signal theRAN (e.g., BS 102) to enquire for the new UE capability information.Accordingly, the RAN may send a UE capability enquiry message to UE. Inresponse the UE may send a UE capability information message, includinga temporary UE radio capability ID, e.g., a new manufacturer-assigned UEradio capability ID, e.g., ID “b”. The temporary ID may be sent with andassociated with the reduced set of UE capability information. The UE mayalso request the AMF (e.g., via RAN) to change from PLMN-assigned ID tothis new manufacturer-assigned ID for a temporary duration (e.g., untilthe thermal and/or other conditions improve).

The AMF may forward the new, temporary manufacturer-assigned ID to theUCMF to create a new dictionary entry in its dictionary via theNucmf_Provisioning_Create_Request service (2128). The AMF may alsoinform the UCMF that from this moment, manufacturer-assigned ID may beused, e.g., until further notice. In some embodiments, the AMF mayspecify a start time for using the manufacturer-assigned ID and/or mayspecify an end time.

The UCMF may create the dictionary entry (2130) and acknowledge to AMFvia Nucmf_Provisioning_Create_Response (2132). The AMF may send aregistration accept including an acknowledgment to the UE of thesuccessful change from PLMN-assigned ID to the temporary (e.g.,manufacturer-assigned) ID (“b”) (2134).

The UE may determine to operate at full capability, e.g., in response toovercoming the thermal condition (e.g., temperature reaching a secondthreshold) or a validity period expiring (2136). In response, the UE maysend a registration request to AMF, e.g., with an NG-RAN RCU flagenabled, e.g., in a “5GS update type” IE (2138). This registrationmessage may inform the network that UE wants to change its UE radiocapability ID and/or capability, e.g., to full capability. For example,the registration message may include the PLMN-assigned UE radiocapability ID (e.g., ID A), e.g., as used prior to the thermalcondition.

In response to the registration request including the PLMN-assigned UEradio capability ID (e.g., ID A), the AMF may transmit a message (e.g.,a Nucmf_UECapabilityManagement_Resolve_Request) to the UCMF includingthe PLMN-assigned UE radio capability ID (e.g., IDA) (2140). In responseto the message, the UCMF may transmit a response (e.g., aNucmf_UECapabilityManagement_Resolve_Respone) to the AMF, e.g.,acknowledging the registration with the PLMN-assigned UE radiocapability ID (e.g., ID A) (2142). In some embodiments, the response mayinclude a description of the capabilities associated with thePLMN-assigned UE radio capability ID (e.g., ID A), e.g., based on thedictionary entry. The AMF may accept the registration (2144) and the UEand RAN may operate according the full capability.

As shown in FIG. 21, and as described above with respect to FIG. 20, aUE 106 may register (2110), the network may create a new dictionaryentry in its dictionary (2112, 2114, 2116), and may send back a newlycreated PLMN-assigned UE radio capability ID (e.g., ID A) (2118, 2120).Later, the UE may determine to operate at a reduced capability (2122)and re-register with a temporary UE radio capability ID (2124). Further,the network may enquire about, and the UE may provide information aboutthe UE's temporary capabilities, as described with respect to FIG. 20.

In response to the updated registration request, the AMF may store thetemporary UE radio capability ID (2226). The AMF may cache the temporaryID locally (e.g., at the AMF) and may not transmit a notification to theUCMF. For example, the AMF may not request that the UCMF create adictionary entry associated with the temporary UE radio capability ID.In some embodiments, the AMF and UE may initiate a validity timerassociated with the temporary UE radio capability ID.

The remainder of FIG. 21 may proceed as described above with respect toFIG. 20. The AMF may send an acknowledgment to the UE of the successfulchange from PLMN-assigned ID to the temporary ID (“b”) (2134). Further,the UE may determine to operate at full capability (2136) andre-register (2138). Further, the AMF may inform the UCMF and accept theregistration (2140, 2142, 2144). The UE may communicate with the networkaccording to full capability.

In some embodiments, various changes to technical specifications may bemade, e.g., consistent with the techniques of FIGS. 19-21. For example,in a registration request, a UE may set the “IE Payload Container Type”to “UE Policy Container”. The UE policy container may contain a list ofUE policy section identifiers (UPSI). The UPSI may be made of two parts:PLMN-assigned UE radio capability ID and UE policy section code. In someembodiments, the specification may be changed to state that amanufacturer-assigned ID should also be included in this container. Insome embodiments, the specification may be changed so that a validationtimer should be associated with the temporary manufacturer-assigned UEradio capability ID.

In some embodiments, if the AMF receives a manufacturer-assigned UEradio capability ID with a validation timer assigned to it, the AMF mayinform the UCMF to not create a PLMN-assigned UE radio capability ID.Accordingly, a specification change may include revising the messageused to create new dictionary entry in UCMF (e.g.,Nucmf_Provisioning_Create_Request) to include an IE “create PLMN-ID”which has a binary value indicating whether or not to create a newPLMN-assigned UE radio capability ID. For example, the IE may have value0 or 1, where 0 indicates “do not create PLMN-ID” and 1 indicates“create a PLMN-ID”.

In some embodiments of the method of FIG. 19, the AF may provision theUCMF with a list of UE radio capability descriptions (e.g., similar tothe descriptions of ID 1-ID 7 as described above, among variouspossibilities). Such a list may be provided prior to registration of anyUE of a relevant model. The UCMF may assign PLMN-assigned UE capabilityIDs for each temporary UE radio capability provisioned by AF, which theUE(s) may use dynamically/temporarily, according to conditions. In someembodiments, instead of provisioning a list of UE radio capabilitydescriptions, the AF may provision UCMF with a list ofmanufacturer-assigned UE radio capability IDs (e.g. similar to ID 1-ID 7as described above, among various possibilities) prior to registrationof any UE of a relevant model, which the UE(s) may use dynamically. Insome embodiments, the UCMF may notify the AMF of the list. FIG. 22 is acall flow diagram illustrating example aspects of the method of FIG. 19highlighting such UCMF and/or AF assignment and dynamic UE selection ofIDs, according to some embodiments.

The AF may transmit one or more messages (e.g.,Nucmf_Provisioning_Create_request) to the UCMF (e.g., using the N57interface) to create or provision a set or list of UE radio capabilityIDs, each associated with its corresponding UE capability information(2512). The UCMF may acknowledge the request(s) (e.g.,Nucmf_Provisioning_Create_Response) and create corresponding dictionaryentry (entries) and UE radio capability IDs (2514). It will beappreciated that 2512 and 2514 can be performed once to create aplurality of UE radio capability IDs or 2512 and 2514 can be performed aplurality of times, e.g., for a single UE radio capability ID of the setor list of IDs each time. It will be appreciated that 2512 may beperformed in response to input from a manufacturer server 109. Thus, theset or list of UE radio capability IDs may include manufacturer-assignedUE radio capability IDs and/or PLMN-assigned UE radio capability IDs.For example, the set or list of UE radio capability IDs may include theseven UE radio capability IDs described above, e.g., in the introductionof FIG. 19, among various possibilities. Note that other UE radiocapability IDs may be used in addition to or instead of the providedexamples.

The UCMF may transmit a message (e.g.,Nucmf_UECapabilityManagement_Subscribe) informing the AMF of the createddictionary entries and UE radio capability IDs (2516). Note that asubscribe message may be used to inform or notify the AMF of creation ordeletion of an entry in the UCMF. The AMF may maintain a list of the(e.g., PLMN-assigned) UE radio capability IDs and/or TAC valuescorresponding to the UE types for which the PLMN usesmanufacturer-assigned UE radio capability IDs.

During an (e.g., initial) registration procedure, the UE may send a(e.g., manufacturer or PLMN-assigned) UE radio capability ID (e.g., IDa) which may contain the full UE capability information, to the AMF(2518).

In response to the registration, the AMF may enquire with the UCMF tocheck if the UE capability information is present in its dictionary(2520). In response to the enquiry, the UCMF may retrieve the (e.g.,manufacturer or PLMN-assigned) UE radio capability ID and provide it tothe AMF, e.g., via the Nucmf_UECapabilityManagement (Assign) service(2522). The AMF may transmit a registration accept message to the UE andmay provide the UE radio capability ID (2524). In some embodiments, theAMF may also inform the UE of the set of UE radio capability IDs and theassociated capabilities. In some embodiments, the AMF may use theregistration accept message to request the UE to delete one or more(e.g., potentially all) PLMN-assigned UE radio capability IDs, e.g., ifthe UE registers with a PLMN-assigned UE radio capability ID for whichthe PLMN uses a manufacturer-assigned UE radio capability ID.

The UE may determine to operate according to reduced capability for aperiod of time (e.g., when the UE detects thermal conditions) (2526).Thus, the UE may send a registration request to AMF with NG-RAN RCU flagenabled in “5GS update type” IE (2528). This message may inform thenetwork that UE wants to change its UE radio capability ID, e.g., to oneof the IDs of the set of UE radio capability IDs. For example, the UEmay compare its temporary capabilities to the capabilities of the set ofUE radio capability IDs and may select a temporary ID best matching itstemporary capabilities. The UE may indicate the selected temporary UEradio capability ID to the network. In some embodiments, the UE mayfurther provide the restricted/reduced capability information inaddition to (or instead of) the selected ID.

The AMF may enquire with the UCMF to confirm that the UE capabilityinformation is present in its dictionary (2530), e.g., associated withthe temporary ID. The UCMF may retrieve the corresponding UE radiocapability ID and provide it to the AMF via theNucmf_UECapabilityManagement (Resolve) service (2532).

The AMF may accept the registration (2534) and may confirm that theselected temporary UE radio capability ID for the new UE capabilityinformation is valid. The UE may continue to communicate with thenetwork using the temporary reduced capability and the temporary ID.

The remainder of FIG. 22 may proceed as described above with respect toFIG. 20. The UE may determine to operate at full capability (2136) andre-register (2138). Further, the AMF may inform the UCMF (2140, 2142)(not shown). Further, the AMF may accept the registration (2144). The UEmay communicate with the network according to full capability.

It will be appreciated that FIG. 22 may refer to manufacturer-assignedand/or PLMN-assigned UE radio capability IDs.

FIG. 23 is a call flow diagram illustrating example aspects of themethod of FIG. 19, according to some embodiments.

As shown, an AF may transmit a Nucmf_Provisioning_Create_Request to theUCMF (e.g., using the N57 interface) to create a set of UE radiocapability IDs (2606, 2610)). The request may be a single request (e.g.,for a plurality of IDs) or may be multiple requests (e.g., one requestper ID). For example, in the case of a single request, the AF may addmultiple different UE capability information descriptions andcorresponding manufacturer-assigned IDs. The AF may provide amanufacturer-assigned UE radio capability ID, e.g., for each requestedPLMN-assigned UE radio capability ID. In some embodiments, amanufacturer-assigned UE radio capability ID may be used as (e.g., maybe the same as a corresponding) PLMN-assigned UE radio capability ID.The AF may provide UE capability information, e.g., for each UE radiocapability ID.

In some embodiments, the AF may provide a validity period (e.g.,duration of a timer) associated with each UE radio capability ID (e.g.,as shown in 2606). In some embodiments, the validity period may bedifferent for each UE radio capability ID. The validity period maydepend on the type of conditions under which each UE radio capability IDmay be used. In some embodiments, the validity may be the same for twoor more UE radio capability IDs, e.g., all UE radio capability IDs mayhave the same validity period, e.g., a standard validity period. In someembodiments, if a manufacturer-assigned UE radio capability ID isassociated with a validity timer, the UCMF may not assign aPLMN-assigned UE radio capability ID to the corresponding capabilities.

The UCMF may respond with a Nucmf_Provisioning_Create_Response (2608,2612). In response to a request that includes a validity timer (2606),the response may indicate that no PLMN-assigned UE radio capability IDis assigned (2608). In response to a request that does not include avalidity timer (2610), the response may indicate that a dictionary entryand a corresponding PLMN-assigned UE radio capability ID is created(2612).

Additional Information and Examples

In some embodiments, during the initial registration procedure, thenetwork may provide the UE with various PLMN-assigned UE radiocapability IDs, e.g., similar to those listed above. The network mayalso provide descriptions of the capabilities associated with each ID,e.g., as discussed above. Thus, the UE and the network may share a listof potential UE radio capability IDs for the UE and the capabilitiesassociated with each UE radio capability ID.

It will be appreciated that various messages are described as beingbetween a UE (or UEs) and various network elements. It will beappreciated that such messages may be transferred through the RAN (e.g.,a BS 102) and/or other elements of the network. For example, to transmitan uplink message “to” the AMF (or any other network element), a UE maysend the message to a BS 102, which may relay the message (e.g.,potentially through one or more intermediate network elements) to theAMF (or other network element). Similarly, downlink messages to a UE maybe relayed from an element of the core network (or a manufacturer server109) through any number of network elements to a BS 102 for transmissionto the UE.

In a first set of embodiments, a method for operating a serverassociated with a user equipment device (UE) manufacturer may comprise:at the server: receiving an updated UE radio configuration; creating aUE radio capability identifier (ID) based on the updated UE radioconfiguration; transmitting the UE radio capability ID to a cellularnetwork; and transmitting the updated UE radio configuration to aplurality of UEs operating on the cellular network.

In some embodiments, the UE radio capability ID may be further based ona type allocation code and software version number, wherein the updatedUE radio configuration does not change the software version number.

In some embodiments, the UE radio capability ID may be further based ona model ID and a software version number, wherein the model IDidentifies a UE model of the UE, wherein the updated UE radioconfiguration does not change the software version number.

In some embodiments, an opcode may be used to describe the updated UEradio configuration.

In a second set of embodiments, a method for operating a server of auser equipment device (UE) manufacturer, may comprise: at the server:receiving a forced capability update; transmitting, to a network elementof a cellular network, information about the capability update, whereinthe information includes a manufacturer-assigned UE radio capabilityidentifier (ID); receiving, from the network element, a confirmation inresponse to the information; and in response to receiving theconfirmation, transmitting, to a plurality of UEs operating on thecellular network, the forced capability update and a second UE radiocapability ID associated with the capability update.

In some embodiments, transmitting the forced capability update mayinclude transmitting an indication to the plurality of UEs to delete aprevious UE radio capability ID.

In some embodiments, the confirmation may be an indication that aplurality of other network elements have received the information aboutthe capability update.

In some embodiments, the manufacturer-assigned UE radio capability IDmay be based on the forced capability update.

In some embodiments, the forced capability update does not update asoftware version number, wherein the manufacturer-assigned UE radiocapability ID is further based on the software version number.

In some embodiments, the second UE radio capability ID may be themanufacturer-assigned UE radio capability ID.

In some embodiments, the second UE radio capability ID may bePLMN-assigned and corresponds to the manufacturer-assigned UE radiocapability ID.

In a third set of embodiments, an apparatus for operating a networkelement of a cellular network, may comprise: a processor configured tocause the network element to: receive a message about a registrationrequest of a first user equipment device (UE) of a first model;determine a first UE radio capability identifier (ID) for UEs of thefirst model; receive information related to a capability update for UEsof the first model; determine a second UE radio capability ID for UEs ofthe first model based on the capability update, wherein the second UEradio capability ID is different from the first UE radio capability ID;receive a second message about a second registration request of a secondUE of the first model; cause a base station of the cellular network tocommunicate with the first UE according to capabilities associated withthe first UE radio capability ID; and cause the base station of thecellular network to communicate with the second UE according tocapabilities associated with the second UE radio capability ID.

In some embodiments, the processor may be further configured to causethe network element to: determine that the first UE has not implementedthe capability update; and determine that the second UE has implementedthe capability update.

In some embodiments, the second message may include the second UE radiocapability ID, wherein the determination that the second UE hasimplemented the capability update is based on the second messageincluding the second UE radio capability ID.

In some embodiments, the processor may be further configured to causethe network element to: at a later time: receive a third massage about are-registration request of the first UE, wherein the third messageincludes the second UE radio capability ID; determine that the first UEhas implemented the capability update, wherein the determination thatthe first UE has implemented the capability update is based on the thirdmessage including the second UE radio capability ID; and cause the basestation of the cellular network to communicate with the first UEaccording to capabilities associated with the second UE radio capabilityID.

In some embodiments, the capabilities associated with the second UEradio capability ID may be based on the capability update, wherein thecapabilities associated with the first UE radio capability ID are notbased on the capability update.

In a fourth set of embodiments, a user equipment device (UE), maycomprise: a radio; and a processor operably connected to the radio andconfigured to cause the UE to: register with a base station of acellular network using an initial UE radio capability ID; communicatewith the base station at a full capability according to the initial UEradio capability ID; determine to operate at a reduced capability on atemporary basis; select a second UE radio capability ID according to thereduced capability; re-register, with the base station, using the secondUE radio capability ID; communicate with the base station at the reducedcapability according to the second UE radio capability ID; determine toresume operation at the full capability; and in response to thedetermination to resume operation at the full capability, revert to theinitial UE radio capability ID.

In some embodiments, the processor may be further configured to causethe UE to: transmit an information element describing a validity timerassociated with the second UE radio capability UE.

In some embodiments, the determination to resume operation at the fullcapability may be based on expiration of the validity timer.

In some embodiments, to revert to the initial UE radio capability IDdoes not include re-registration with the base station using the initialUE radio capability ID.

In some embodiments, the determination to resume operation at the fullcapability may be based on a change in conditions at the UE prior toexpiration of the validity timer.

In some embodiments, the determination to operate at the reducedcapability on the temporary basis may be based on a temperature at acomponent of the UE reaching a temperature threshold.

Embodiments of the present disclosure may be realized in any of variousforms. For example, some embodiments may be realized as acomputer-implemented method, a computer-readable memory medium, or acomputer system. Other embodiments may be realized using one or morecustom-designed hardware devices such as ASICs. Still other embodimentsmay be realized using one or more programmable hardware elements such asFPGAs.

In some embodiments, a non-transitory computer-readable memory mediummay be configured so that it stores program instructions and/or data,where the program instructions, if executed by a computer system, causethe computer system to perform a method, e.g., any of a methodembodiments described herein, or, any combination of the methodembodiments described herein, or, any subset of any of the methodembodiments described herein, or, any combination of such subsets.

In some embodiments, a device (e.g., a UE) may be configured to includea processor (or a set of processors) and a memory medium, where thememory medium stores program instructions, where the processor isconfigured to read and execute the program instructions from the memorymedium, where the program instructions are executable to implement anyof the various method embodiments described herein (or, any combinationof the method embodiments described herein, or, any subset of any of themethod embodiments described herein, or, any combination of suchsubsets). The device may be realized in any of various forms.

It is well understood that the use of personally identifiableinformation should follow privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. In particular,personally identifiable information data should be managed and handledso as to minimize risks of unintentional or unauthorized access or use,and the nature of authorized use should be clearly indicated to users.

Although the embodiments above have been described in considerabledetail, numerous variations and modifications will become apparent tothose skilled in the art once the above disclosure is fully appreciated.It is intended that the following claims be interpreted to embrace allsuch variations and modifications.

1.-20. (canceled)
 21. A network element, comprising: an interface; and aprocessor operably coupled to the interface and configured to cause thenetwork element to: receive a first UE radio capability identifier (ID)from a user equipment (UE) corresponding to a first version number;transmit the first UE radio capability ID to a UE radio CapabilityManagement Function (UCMF); receive an updated UE radio capability IDbased on an updated UE radio configuration from the UCMF correspondingto a second version number previously stored at the UCMF, wherein theupdated UE radio capability ID is a public land mobile network (PLMN)assigned UE radio capability ID and is assigned by the UCMF; andtransmit the updated UE radio capability ID to the UE through a cellularnetwork.
 22. The network element of claim 21, wherein the updated UEradio capability ID further includes an identifier associated with acapability update of the second version number.
 23. The network elementof claim 22, wherein the updated UE radio configuration does not changea software version number.
 24. The network element of claim 21, whereinan opcode is used to describe the updated UE radio configuration. 25.The network element of claim 21, wherein the first UE radio capabilityID is further based on an identification of a manufacturer.
 26. Thenetwork element of claim 21, wherein the updated UE radio capability IDis further based on an identification of a manufacturer.
 27. The networkelement of claim 21, wherein the network element comprises an Access andMobility Management Function.
 28. A user equipment device (UE),comprising: a radio; and a processor configured to cause the UE to:transmit, through a cellular network, a first UE radio capabilityidentifier (ID) to an Access and Mobility Management Function (AMF)corresponding to a first version number; and receive, through thecellular network, an updated UE radio capability ID from the AMF basedon an updated UE radio configuration from a UE radio CapabilityManagement Function (UCMF) corresponding to a second version numberpreviously stored at the UCMF, wherein the updated UE radio capabilityID is a public land mobile network (PLMN) assigned UE radio capabilityID and is allocated by the UCMF.
 29. The UE of claim 28, wherein theupdated UE radio capability ID further includes an identifier associatedwith a capability update of the second version number.
 30. The UE ofclaim 29, wherein the updated UE radio configuration does not change asoftware version number.
 31. The UE of claim 28, wherein an opcode isused to describe the updated UE radio configuration.
 32. The UE of claim28, wherein the first UE radio capability ID is further based on anidentification of a manufacturer.
 33. The UE of claim 28, wherein theupdated UE radio capability ID is further based on an identification ofa manufacturer.
 34. A base station, comprising: a radio; and a processoroperably coupled to the radio and configured to cause the base stationto: receive a first UE radio capability identifier (ID) from a userequipment (UE) corresponding to a first version number; transmit thefirst UE radio capability ID to a core network; receive, from the corenetwork, an updated UE radio capability ID based on an updated UE radioconfiguration corresponding to a second version number previously storedat the core network, wherein the updated UE radio capability ID is apublic land mobile network (PLMN) assigned UE radio capability ID and isassigned by the core network; and transmit the updated UE radiocapability ID to the UE.
 35. The base station of claim 34, wherein theupdated UE radio capability ID further includes an identifier associatedwith a capability update of the second version number.
 36. The basestation of claim 35, wherein the updated UE radio configuration does notchange a software version number.
 37. The base station of claim 34,wherein an opcode is used to describe the updated UE radioconfiguration.
 38. The base station of claim 34, wherein the first UEradio capability ID is further based on an identification of amanufacturer.
 39. The base station of claim 34, wherein the updated UEradio capability ID is further based on an identification of amanufacturer.
 40. The base station of claim 34, wherein the first UEradio capability ID is transmitted to an Access and Mobility ManagementFunction of the core network.